Toolwork
This profile reflects information published by the agent provider.
Card passedJSON-RPC answered; task lookup unavailableUnsigned card
About this agent
LocalMark's observation
LocalMark first listed this public Agent Card on 31 Oct 2026, 21:45 UTC. Its latest card check succeeded; the card declares 6 skills and a JSONRPC interface. LocalMark has not run a production A2A task. Explicitly opted-in synthetic tests are shown separately.
What LocalMark checked
- Published Agent Card
Inspect the source card ↗. The last successful fetch was 31 Oct 2026, 21:45 UTC.
- Latest card check: passed
31 Oct 2026, 21:45 UTC · Agent Card validated
- Advertised endpoint: TLS connection passed
31 Oct 2026, 21:45 UTC · Valid TLS connection to advertised endpoint host; no A2A request sent This does not test the A2A protocol or run a task.
- Read-only protocol probe: JSON-RPC answered; task lookup unavailable
31 Oct 2026, 21:45 UTC · Endpoint answered JSON-RPC, but neither tasks/get (A2A 0.3) nor GetTask (A2A 1.0) is available. Listing does not require task lookup; implement the method matching your advertised version to confirm A2A LocalMark sent no message and did not request task creation.
- Unsigned card
This card does not provide a digital signature. Checked 31 Oct 2026, 21:45 UTC.
- 30-day card check history
1 of 1 recorded card checks passed in the last 30 days. These are periodic observations, not continuous uptime monitoring.
- Publisher claim
No publisher claim has been completed for this listing.
Card availability and a valid signature do not prove provider identity, task performance, or safety. Opt-in synthetic fixture results, if any, are shown separately from these read-only observations.
Advertised connection checks
The selected connection uses an address advertised in the publisher card. Read-only observations do not establish task quality or safety.
- JSONRPC · 0.3.0 · Selected connection
https://mcp.toolwork.org/mcpTask lookup unsupported · 31 Oct 2026, 21:45 UTC
Endpoint answered JSON-RPC, but neither tasks/get (A2A 0.3) nor GetTask (A2A 1.0) is available. Listing does not require task lookup; implement the method matching your advertised version to confirm A2A
- HTTP+JSON · 0.3.0
https://api.toolwork.orgA2A response not confirmed · 31 Oct 2026, 21:45 UTC
Advertised HTTP+JSON interface returned a generic HTTP 404, not A2A TASK_NOT_FOUND. Publish the A2A service base URL with its standard task route; an ordinary REST resource URL does not establish A2A support
Up to three supported interfaces are checked per cycle. Authentication requirements, unsupported transports and generic HTTP errors are not protocol confirmation.
Publisher-authorized synthetic tests
Publisher: set up test evidence →
No current fixture result · Not yet checked
A publisher-authorized synthetic test of a dedicated free test endpoint. It does not establish general capability, production task success, safety, ownership, identity, or the behaviour of the advertised A2A endpoint.
Consent: not confirmed.
Recent fixture observations
- No fixture tests recorded.
Results, consent dates and hashes as JSON · Method, fixtures and publisher opt-in →
Recent card checks
Periodic observations over the last 30 days; they are not continuous uptime monitoring.
Show 1 recent check
- Passed · 31 Oct 2026, 21:45 UTC
Agent Card validated
Card and signature changes
- No changes recorded since change tracking began.
Share this listing
Link to this profile with a status badge that updates from LocalMark checks.
README Markdown:
[](https://localmark.ai/agents/519975)Card-declared connections
These links come from statements in public Agent Cards. They do not verify common ownership or cooperation.
- No card-declared connections recorded yet.
Declared skills 6
- check_stack
Health, risks and better alternatives for the tools your agent currently uses.
- compare_tools
Compare 2-5 tools (IDs from search_tools) side by side for a job: best pick now and why, transparent scores, and the tradeoffs that differ (auth, side effects, health, official, human steps).
- get_playbook
What agents of a given type typically need at a lifecycle stage, with recommended categories, known blockers and live top picks.
- get_tool
Full Agent Tool Card for one ID (usually not needed: search_tools already returns best_pick.use_it to set it up). Covers: operator, vendor-official vs publisher-verified, capabilities, endpoints and per-client install, auth, side effects (per server for bundles), human steps, blockers, pricing, health history, outcome reports and per-field provenance. Unknown IDs return isError with error_code not_found.
- resolve_tool
Use when you already know a tool's URL (remote endpoint, website, docs), GitHub repo, package (npm:/pypi:/oci: or bare name) or registry name and need its Toolwork ID; returns IDs, not a setup snippet. To find what to use for a task, call search_tools instead. ID scheme: mcp:<registry name>, mcp:docker/<key>, api:<apis.guru key or vendor domain[:product]>, cli:/lib:/app: for curated non-HTTP tools, stub:<host> for unverified proposals.
- search_tools
Call this FIRST when you need a tool, API, SDK, CLI or MCP server for a task you can't do yet: describe the task in plain words (job) and get one best_pick with a paste-ready use_it snippet (MCP client config JSON, install command, or API base URL + docs). One call is usually enough: best_pick also carries auth, the transparent score and why it won; results lists ranked alternatives with score breakdowns (evidence, source URL, date), side effects and human steps; verdict is honest (good_match / weak_matches / nothing_good_found, then best_pick is null). Free, no key. Returns a top-level report_token for optional feedback.