Skip to main content
Glama

Get a source

get_source
Read-only

Gives one catalogue entry in full, with its editions and how Scamstats uses it, from its id.

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": {
      "id": "<id>"
    },
    "name": "get_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe catalogue entry id, as search_sources gives it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful content disclosure (the entry comes back in full, including editions and how Scamstats uses it), but says nothing about error behavior for a missing id or the potential size of the editions list.

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?

One sentence, front-loaded with the action and resource, with no filler. The phrase 'how Scamstats uses it' is slightly loose but still informative rather than wasted.

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 simple read-only, single-parameter lookup with no output schema, the description covers what is returned and how the id is obtained. The remaining gap—behavior on a nonexistent id—is minor for this complexity level.

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 single parameter is fully documented there, including its provenance from search_sources. The description's 'from its id' merely restates the schema, adding no format or validation detail beyond it.

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?

States a specific verb and resource ('Gives one catalogue entry in full') plus what the payload contains (editions, Scamstats usage) and the key it is fetched by. It does not explicitly contrast itself with the sibling get_* / search_* tools, so an agent must infer that this is the detail-fetch counterpart to search_sources.

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: 'from its id' combined with the schema note that the id is 'as search_sources gives it' suggests the search-then-fetch workflow. There is no explicit statement of when to use this versus search_sources, and no mention of what to do when the id is unknown or invalid.

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