Skip to main content
Glama

Discover the Tools

get_tool

Read-onlyIdempotent

Get one public listing, pricing evidence, dates and sponsorship disclosure. Does not freshly verify vendor claims.

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
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds genuinely new behavioral context with "Does not freshly verify vendor claims," warning the agent that the evidence may be stale — a freshness caveat annotations cannot express. It stops short of explaining caching or refresh paths.

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 short sentences, front-loaded with the action and payload, followed by the caveat. The field enumeration is dense but every element earns its place by substituting for a missing output schema.

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 one-parameter read tool with no output schema, the description usefully previews the returned fields and flags data freshness. The only real gap is the lack of explicit slug semantics and not-found behavior.

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 0%, so the schema's pattern and maxLength convey format but not meaning. The description says "one public listing" which hints the single slug identifies a listing, but it never explicitly ties the parameter to a slug identifier or explains what happens if the listing is absent.

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?

Specific verb and cardinality: "Get one public listing" and it enumerates the returned facets (pricing evidence, dates, sponsorship disclosure). "One" implicitly contrasts with the search/compare siblings, 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 Guidelines3/5

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

Usage is only implied — the singular lookup framing suggests fetching a known listing rather than searching or comparing. There is no explicit when-to-use or when-not-to-use guidance relative to search_tools, compare_tools, or check_tool_listing.

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