Skip to main content
Glama
chrischall

thumbtack-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

thumbtack_graphql

Read-only

Run read-only GraphQL queries against Thumbtack's anonymous endpoint for profiles, ratings, reviews, and credentials. Mutations are rejected; introspection is off, so supply fields from page state.

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

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.4/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses decisive behavioral constraints: introspection is disabled upstream, field names must be sourced from a page's Apollo state, and mutations are refused. These are exactly the facts an agent needs to avoid failing calls, and they are not encoded in any structured field.

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 tight sentences, front-loaded with the identifying phrase 'Escape hatch,' and every clause carries distinct information (scope, introspection limitation, mutation refusal). No filler.

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-query tool with no output schema (return shape is defined by the caller's query), the description covers the critical constraints but says nothing about error behavior, variable handling, or pagination. Adequate to call correctly, with minor gaps.

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 the 'view' enum is well documented in-schema (compact vs full projection behavior). The description adds no parameter-level detail of its own, so the baseline of 3 applies – the heavy lifting is done by the schema.

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?

States a specific verb and resource ('issue an arbitrary read-only query against Thumbtack's anonymous GraphQL endpoint') and frames itself as an 'escape hatch,' which immediately distinguishes it from the purpose-built siblings like thumbtack_search_pros. An agent can tell what it does and where it sits relative to the others without opening the schema.

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?

The word 'escape hatch' plus 'read-only' gives clear context for when this is appropriate (arbitrary queries the purpose-built tools don't cover). It does not, however, explicitly name an alternative tool or a fallback rule such as 'prefer thumbtack_search_pros for normal searches,' so it stops just short of full routing guidance.

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