Skip to main content
Glama
Sign In

Pineprompt

by com.pineprompt
OverviewDiscussionsAdmin

Get Citation Tool

get-citation-tool
Read-onlyIdempotent

Fetch a single citation by its numeric id. Optionally pass include to load parent chains.

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": {
      "citation_id": "<citation_id>"
    },
    "name": "get-citation-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeNoOptional comma-separated related resources to include in the response. Whitelisted: `response`, `response.prompt`, `response.monitor`, `response.project`, `source_url`, `source_url.source`, `source_url.source.project`.
citation_idYesThe numeric id of the citation to fetch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add beyond that. It adds the useful detail that `include` expands into parent chains, but says nothing about behavior on an unknown id or what a citation record contains.

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 core action and followed by the optional parameter note. No filler, though the sentence about `include` largely restates what the schema already marks as optional.

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 single-record fetch with full schema coverage and clear annotations, this is adequate. The remaining gap is that with no output schema, the description could briefly describe what a citation returns, especially when expansions are requested.

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 100%, so both parameters are already documented, giving a baseline of 3. The phrase "load parent chains" adds a small amount of meaning about why one would use `include`, but the whitelisted values themselves are only in the schema.

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 ("Fetch a single citation by its numeric id") which is enough to distinguish it from the sibling get-* tools that target other resources like prompts, monitors, and sources. It stops short of any explicit differentiation from other citation-adjacent operations, but the purpose itself is unambiguous.

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 about when to use this versus any alternative, or any precondition such as needing an id obtained from a list/search call. The only usage-like statement is that `include` is optional, which is parameter-level rather than tool-selection guidance.

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

All Pineprompt 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