Skip to main content
Glama

Get one listing

get_tool
Read-onlyIdempotent

One listing in full by slug (or a package, GitHub owner/repo or registry name): grade, the reason and sources for each score, how to connect, auth, prices and who is behind it. Use it for one named tool.

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": {
      "slug": "<slug>"
    },
    "name": "get_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesListing slug, e.g. exa-mcp, or a package, GitHub owner/repo or registry name
formatNojson (the default), markdown, or slim for the fewest tokens
includeNojson only: parts left out to keep the answer short, as omitted lists; all for everything

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / include / description
      Previous value: -"json only: reviews, audience reviews, rulings or live history, left out by default for size"New value: +"json only: parts left out to keep the answer short, as omitted lists; all for everything"
    • changedInput schema / properties / include / items / enum
      Previous value: -[
      -  "reviews",
      -  "audienceReviews",
      -  "arbiter",
      -  "live",
      -  "all"
      -]New value: +[
      +  "reviews",
      +  "audienceReviews",
      +  "arbiter",
      +  "live",
      +  "assessment",
      +  "history",
      +  "policies",
      +  "people",
      +  "mcpTools",
      +  "sources",
      +  "details",
      +  "notable",
      +  "provenance",
      +  "setup",
      +  "deprecations",
      +  "compliance",
      +  "unitPrices",
      +  "strengths",
      +  "all"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / include / description
      Previous value: -"json only: parts left out by default because they're most of the size, the reviews in full, the audience reviews, the arbiter's rulings and the live record's history"New value: +"json only: reviews, audience reviews, rulings or live history, left out by default for size"
    • changedInput schema / properties / slug / description
      Previous value: -"Listing slug, e.g. exa-mcp, or a name it goes by: a package (@ai-sdk/gateway), a GitHub owner/repo, or a registry server name"New value: +"Listing slug, e.g. exa-mcp, or a package, GitHub owner/repo or registry name"
  3. Changed1 schema field changed
    • addedInput schema / properties / include
      Added value: +{
      +  "description": "json only: parts left out by default because they're most of the size, the reviews in full, the audience reviews, the arbiter's rulings and the live record's history",
      +  "items": {
      +    "enum": [
      +      "reviews",
      +      "audienceReviews",
      +      "arbiter",
      +      "live",
      +      "all"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so safety is covered. The description adds real value by disclosing what comes back (scores with reasons and sources, connection/auth details, prices, ownership), but says nothing about response size, latency, or when an unknown slug results in an error.

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 tight sentences, with the resource and identifier front-loaded and the usage rule last. The parenthetical and the comma-separated payload list are dense but every item is informative; nothing is redundant 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?

With no output schema, the description carries the burden of describing the return payload and does so explicitly, covering scores, sources, setup/auth, pricing and ownership. It is complete enough for an agent to call correctly, with minor gaps only around error behavior and the effect of `include` omissions.

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%, so all three parameters are documented in structured fields, giving a baseline of 3. The description restates the slug's flexibility (slug, package, GitHub owner/repo, registry name) but adds nothing about `format` or `include` beyond what the schema already says.

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

Purpose4/5

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

The description states a specific verb+resource — fetch one listing in full by slug — and enumerates the returned content (grade, per-score reasons and sources, connect, auth, prices, who is behind it). 'Use it for one named tool' implicitly separates it from discovery siblings like search_tools, though it never names them.

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?

'Use it for one named tool' sets a clear usage context that contrasts with search/list workflows. It stops short of explicit exclusions or naming an alternative (e.g. search_tools for discovery), so the agent must infer the boundary.

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