Skip to main content
Glama

SubscriptionFlow

Fetch a knowledge article

fetch
Read-only

Fetch one published SubscriptionFlow knowledge article by id (an id returned by search). Draft or unknown ids are not found. Public, read-only.

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": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesKnowledge article id from `search`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/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 safety is covered. The description still adds real behavioral value by limiting results to published articles and disclosing that draft and unknown ids return not-found — a failure mode an agent needs to handle. It does not describe the returned article shape, which keeps it from a 5.

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?

Two tight sentences with the resource and key front-loaded, followed by the not-found caveat. Nothing is redundant except the trailing 'Public, read-only', which briefly echoes the annotations.

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 single-parameter read tool with full schema coverage and complete annotations, the description covers what is needed to invoke it correctly, including the published-only constraint. The one gap is that it says nothing about what the fetched article contains, though with no output schema that is a minor omission.

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 schema property already says 'Knowledge article id from `search`', so the description's 'an id returned by `search`' largely restates it. The added meaning — that the id must belong to a published article — is useful but marginal, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — fetch one published SubscriptionFlow knowledge article — and pins the lookup key to an id. The 'by id' framing cleanly distinguishes it from the sibling `search` tool, which returns ids rather than article bodies.

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

Usage Guidelines4/5

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

Explicitly routes the agent through `search` first by requiring 'an id returned by `search`', and warns that draft or unknown ids are not found, which is an effective usage constraint. It stops short of naming a full alternative or stating what to do when the fetch fails, so it is clear context rather than exhaustive when/when-not guidance.

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