Skip to main content
Glama

Find a vendor API endpoint

vendors
Read-only

Find a vendor API and matching endpoints to call with your own credentials. Search by query or category, then inspect endpoints and make the call.

Instructions

Find a vendor API (Google Ads, Datadog, ...) to call with the user's own credentials. With 'query', matching endpoints, best first; without, the vendors. Then 'vendor_endpoint' and 'call_vendor'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vendors"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost endpoints to list; 20 unset.
queryNoWhat you want, in words, e.g. 'google ads spend by campaign'.
vendorNoOnly this vendor's endpoints (its slug, e.g. 'google-ads').
categoryNoOnly vendors on this shelf.
configuredNoWhen listing vendors: true for the ones whose credentials are set here, false for the rest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds that credentials are the user's own, that results are relevance-ordered, and that this is a lookup step feeding vendor_endpoint/call_vendor. It doesn't say anything about result volume or empty-result behavior, which keeps it from a 5.

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

Conciseness4/5

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

Two sentences, front-loaded with purpose, no filler. The telegraphic phrasing ("With 'query', matching endpoints, best first; without, the vendors") is efficient but slightly elliptical and reads a bit like shorthand, which costs it a point.

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 five-parameter, all-optional, read-only discovery tool with no output schema, the description covers purpose, both modes, and the downstream workflow adequately. Minor gaps around result limits and the configured/category filters are handled by the schema, not the description.

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

Parameters4/5

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

Schema coverage is 100%, so a 3 baseline applies, but the description genuinely adds meaning by explaining how supplying 'query' versus omitting it changes what the tool returns (endpoints vs. vendors), which the schema's field descriptions do not state. It stays silent on limit, vendor, category and configured, but those are documented in 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 concrete verb+resource ("Find a vendor API ... to call with the user's own credentials") and immediately distinguishes its role from the follow-on tools vendor_endpoint and call_vendor. An agent can tell this is the discovery step without opening any 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?

Gives explicit conditional behavior: with 'query' you get matching endpoints ranked best-first, without 'query' you get the vendor list, and it names the follow-on tools to use afterwards. What's missing is any statement of when not to use it (e.g. going straight to vendor_endpoint when the vendor is already known).

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