Skip to main content
Glama
Sign In

SpecStream

by ai.specstream
OverviewDiscussionsAdmin

Read a source preview

get_web_source_preview
Read-only

Reads one source preview with its rows, cell locations and field explanations.

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": {
      "preview_id": "<preview_id>"
    },
    "name": "get_web_source_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
preview_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing the return contents, but says nothing about behavior on an unknown or expired preview_id, which matters for a read-by-identifier tool.

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 front-loaded sentence naming the operation and the returned components, with no filler. Slightly list-like, but every clause earns its place.

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?

No output schema exists, and the description does cover what the response contains, which is the main completeness need. Missing is how to obtain a valid preview_id and what happens when the preview is absent or stale, both of which an agent needs before calling.

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?

The single parameter preview_id has 0% schema description coverage, so the description carries the burden and does not compensate: it never says where a preview_id comes from, its format, or its lifetime. The agent is left to infer the identifier's provenance from adjacent tools.

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 ('Reads one source preview') and enumerates the payload (rows, cell locations, field explanations), so the agent knows what it gets back. It does not differentiate from the near-name siblings preview_web_source and get_web_source, which is the only clarity gap.

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?

There is no guidance on when to use this versus preview_web_source (likely the producer of a preview) or get_web_source (likely the source definition). Usage is only inferable from the required preview_id, so the agent must guess the workflow position.

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

All SpecStream toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources