Verify Thumbtack's anonymous reachability and expected response shape, reporting server version, HTML page probe, and GraphQL probe separately.
Check that Thumbtack's anonymous surface is reachable and still has the response shape this server expects. Reports the server version, the HTML page probe and the GraphQL probe separately.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.5Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnlyHint=true and the title 'Healthcheck'. The description adds meaningful behavioral context: it probes the HTML page and GraphQL endpoints separately and reports server version plus each probe result. This goes beyond what the structured annotations convey.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no wasted words. The core purpose is front-loaded, and the second sentence explains what the report contains, which is exactly the useful detail an agent needs.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple, parameterless healthcheck tool, this is complete: an agent knows what it does, what it checks, and what kind of output to expect. No output schema is present, but the description names the three reported components (server version, HTML probe, GraphQL probe) sufficiently.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and schema coverage is 100%, so the schema already fully documents the input surface. No parameter explanation is needed, and the baseline of 4 is appropriate for a parameterless tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('check') and a precise resource ('Thumbtack's anonymous surface') plus what 'health' means here: reachability and expected response shape. It is also clearly distinct from the data-fetching siblings like thumbtack_search_pros and thumbtack_get_pro.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description makes it clear that this tool is a diagnostic probe for reachability and response shape, so an agent can infer when to run it before relying on other Thumbtack tools. It does not explicitly state 'use this instead of X' or list exclusions, so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.