Skip to main content
Glama
chrischall

thumbtack-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

thumbtack_graphql

Read-only

Run arbitrary read-only GraphQL queries against Thumbtack's anonymous endpoint to access data not available through standard tools. Mutations are refused.

Instructions

Escape hatch: issue an arbitrary read-only query against Thumbtack's anonymous GraphQL endpoint. Introspection is disabled upstream, so field names must come from a page's Apollo state. Mutations are refused.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact returns the slim projection where one exists and strips image URLs elsewhere; "full" returns Thumbtack's whole records.
queryYesA GraphQL query document. Must not contain a mutation or subscription.
variablesNoVariables for the query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.5
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact returns the slim projection where one exists and strips image URLs elsewhere; \"full\" returns Thumbtack's whole records.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint, so the description adds genuinely useful behavior beyond that: the endpoint is anonymous, introspection is disabled upstream, field names must come from a page's Apollo state, and mutations are refused. These are the critical operational constraints for issuing a raw query. It stops short of describing error shapes or rate limits, but the important behavior is well covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: purpose is front-loaded, then the two most important caveats (introspection disabled, mutations refused). There is no filler and no repetition of schema content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a raw GraphQL escape hatch, the description covers the endpoint, auth expectations (anonymous), field discovery limitation, and mutation prohibition. The only notable gap is that it does not describe the response envelope, but for an arbitrary query tool the result shape is inherently query-dependent, so this is a minor omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and each parameter ('query', 'variables', 'view') already carries a detailed schema description, including the 'compact' vs 'full' response distinction. The description adds no parameter-specific information, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('issue'), a resource ('arbitrary read-only query against Thumbtack's anonymous GraphQL endpoint'), and frames itself as an 'escape hatch.' This clearly differentiates it from the wrapped sibling tools like thumbtack_get_pro and thumbtack_search_pros.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Escape hatch' signals that this tool is the fallback for queries not covered by higher-level wrappers, and 'arbitrary read-only query' sets a clear scope. It does not explicitly name alternatives or list when-not conditions, but the context is unambiguous enough for an agent to route to it appropriately.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools