Skip to main content
Glama

Data catalog and usage

spur_get_data_catalog
Read-onlyIdempotent

Read the full field catalog, live recipes and credit sheets, industry waterfall, or dated data usage. Free.

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": {
      "section": "<section>"
    },
    "name": "spur_get_data_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNo
sectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds one genuinely new behavioral fact — the call is free (no credit consumption) — which is useful for cost-sensitive planning. It does not disclose whether results are static reference data or whether 'usage' requires a date window via 'from'.

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

Conciseness5/5

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

One short sentence, front-loaded with the verb and resource list, with 'Free.' as a deliberate standalone cost note. No filler or redundancy.

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

Completeness3/5

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

For a two-parameter, enum-driven read tool with strong annotations and no output schema, the definition is roughly adequate, but the 0% schema coverage means the undefined 'from' parameter and the unlabeled section values leave real gaps. An agent can guess the section key from the content names but has no basis for using the date filter.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the burden, and it only partially delivers: the four listed content types loosely correspond to the four 'section' enum values but are not named as such. The 'from' date-time parameter — including that it is optional, must be UTC 'Z' format, and presumably bounds the 'usage' section — is not mentioned at all.

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 ('Read') plus four concrete resource types: field catalog, recipes and credit sheets, industry waterfall, and dated data usage. It is clearly a catalog/reference reader, distinct from job-running or analytics siblings. It stops short of 5 because the four content names are never tied to the actual 'section' enum keys (data_points, recipes, segment, usage), so the agent must guess the mapping.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description gives no when-to-use condition, no exclusions, and no routing to alternatives, even though siblings like spur_get_usage_analytics plausibly overlap with the 'dated data usage' section. 'Free' hints at a cost motivation for preferring this tool, but that is a property, not guidance on when to select it.

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