Skip to main content
Glama

Get one vendor

get_vendor
Read-onlyIdempotent

Everything the index knows about one vendor: category, areas, bookability score, website, how to book, and every published fact (starting price and what it covers, packages, deposit, booking lead time, cancellation policy and more), each with the quote from the vendor's own site, its page and the date read. If a name matches several vendors, the error lists them with their index_page. (fetch returns the same facts as text, for ids that came from search.)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vendor": "<vendor>"
    },
    "name": "get_vendor"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendorYesThe vendor's name (or part of it), its index_page URL from another tool, or its slug such as "448-studio".

Output Schema

NameRequiredDescriptionDefault
nameYes
areasYes
factsYesEvery published fact, by name (starting_price, packages, deposit...).
scoreYes
checkedNo
cite_asNoAgent Bookability Index by The Runup (index.therunup.ai)
websiteNo
categoryYes
index_pageYes
how_to_bookYes
price_from_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / vendor / description
      Added value: +"The vendor's name (or part of it), its index_page URL from another tool, or its slug such as \"448-studio\"."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "Booking": {
      +      "properties": {
      +        "contact_methods": {
      +          "description": "Ways to reach the vendor shown on its site (form, email, phone...).",
      +          "items": {
      +            "type": "string"
      +          },
      +          "title": "Contact Methods",
      +          "type": "array"
      +        },
      +        "instant_quote": {
      +          "anyOf": [
      +            {
      +              "type": "boolean"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "description": "The site shows a price after choosing options.",
      +          "title": "Instant Quote"
      +        },
      +        "online_booking": {
      +          "anyOf": [
      +            {
      +              "type": "boolean"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "description": "The vendor's site lets you book online.",
      +          "title": "Online Booking"
      +        },
      +        "quote_request_form": {
      +          "anyOf": [
      +            {
      +              "type": "boolean"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "description": "The site has a form to ask for a quote.",
      +          "title": "Quote Request Form"
      +        },
      +        "shows_open_dates": {
      +          "anyOf": [
      +            {
      +              "type": "boolean"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "description": "The site shows dates that are still open.",
      +          "title": "Shows Open Dates"
      +        }
      +      },
      +      "title": "Booking",
      +      "type": "object"
      +    },
      +    "Fact": {
      +      "properties": {
      +        "checked": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "title": "Checked"
      +        },
      +        "quote": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "description": "The words on that page (emails and phones masked).",
      +          "title": "Quote"
      +        },
      +        "source": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "description": "The vendor's own page the fact was read from.",
      +          "title": "Source"
      +        },
      +        "value": {
      +          "description": "The value as recorded (text, number, list or object).",
      +          "title": "Value"
      +        }
      +      },
      +      "required": [
      +        "value"
      +      ],
      +      "title": "Fact",
      +      "type": "object"
      +    }
      +  },
      +  "properties": {
      +    "areas": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "title": "Areas",
      +      "type": "array"
      +    },
      +    "category": {
      +      "title": "Category",
      +      "type": "string"
      +    },
      +    "checked": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Checked"
      +    },
      +    "cite_as": {
      +      "default": "Agent Bookability Index by The Runup (index.therunup.ai)",
      +      "title": "Cite As",
      +      "type": "string"
      +    },
      +    "facts": {
      +      "additionalProperties": {
      +        "$ref": "#/$defs/Fact"
      +      },
      +      "description": "Every published fact, by name (starting_price, packages, deposit...).",
      +      "title": "Facts",
      +      "type": "object"
      +    },
      +    "how_to_book": {
      +      "$ref": "#/$defs/Booking"
      +    },
      +    "index_page": {
      +      "title": "Index Page",
      +      "type": "string"
      +    },
      +    "name": {
      +      "title": "Name",
      +      "type": "string"
      +    },
      +    "price_from_usd": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Price From Usd"
      +    },
      +    "score": {
      +      "title": "Score",
      +      "type": "integer"
      +    },
      +    "website": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Website"
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "category",
      +    "areas",
      +    "score",
      +    "index_page",
      +    "how_to_book",
      +    "facts"
      +  ],
      +  "title": "VendorDetail",
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world, and non-destructive, so safety needs no restating. The description adds two genuinely non-obvious behaviors: ambiguity handling (if a name matches several vendors, the error lists them with their index_page) and provenance granularity (each fact carries its source quote, page, and date read). It does not discuss pagination or size limits for vendors with many facts, so it is good but not rich.

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

Conciseness3/5

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

The content is front-loaded on what the tool returns, which is the right priority, but the long parenthetical enumeration of facts ('starting price and what it covers, packages, deposit, booking lead time, cancellation policy and more') is wordier than needed given an output schema already documents the payload. The trailing parenthetical about fetch is useful but reads as an afterthought.

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

Completeness5/5

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

For a single-parameter read tool with full annotations, complete schema documentation, and an output schema, the description covers the remaining gaps an agent needs: what the payload contains conceptually, how ambiguity is reported, and which sibling to use instead for search-derived ids. Nothing required for a correct call is missing.

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 coverage is 100% and the schema description already explains that the vendor argument accepts a name, partial name, index_page URL, or slug. The description's only additional parameter-related meaning is that returning multiple matches produces a listing error rather than a guess, which is a modest supplement over 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?

Names a specific verb and resource (get one vendor) and enumerates exactly what comes back: category, areas, bookability score, website, how to book, and every published fact with source quote, page, and date read. It also distinguishes itself from the sibling 'fetch' by stating that fetch returns the same facts as text for ids that came from search.

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?

Usage context is clear — this is the lookup for a single known vendor — and the alternative path to 'fetch' is named with the condition that selects it (ids originating from search). It does not explicitly say when not to use it, e.g. that list/browse queries belong to search_vendors, so it stops 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources