Skip to main content
Glama

SW Accounting documentation

Fetch a document

fetch_doc
Read-onlyIdempotent

Return one page or article of sw-cpas.com as markdown with YAML front matter. Accepts a full URL or a path such as /dental-cpa/ or /agents.md, usually taken from search_docs results. URLs on other sites are refused.

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": {
      "url": "<url>"
    },
    "name": "fetch_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL or path on sw-cpas.com, e.g. /services/ or https://sw-cpas.com/agents.md.

Output Schema

NameRequiredDescriptionDefault
urlYesCanonical URL of the document.
titleNoDocument title.
markdownYesFull text as markdown with YAML front matter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond that: the response is markdown with YAML front matter, and off-site URLs are rejected rather than fetched, which tells the agent how failures will look.

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?

Three short sentences, front-loaded with the return format and scope, then input forms, then the constraint. No filler and nothing repeated from the schema.

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

Completeness5/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 an output schema and full annotation coverage, the description supplies everything an agent needs: what comes back, what inputs are valid, where to get them, and what is rejected.

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

Parameters4/5

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

Schema coverage is 100% and the schema already gives examples, so the baseline is 3. The description goes further by explaining where the url value typically comes from (search_docs results) and the domain restriction that governs valid values, adding meaning the schema does not encode.

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 ('Return one page or article of sw-cpas.com') plus the exact output format (markdown with YAML front matter), which distinguishes it from the sibling search_docs, a discovery tool rather than a retrieval one.

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?

Explains the accepted input forms (full URL or path like /dental-cpa/ or /agents.md) and points to search_docs as the usual source of those URLs, plus an explicit exclusion: 'URLs on other sites are refused.' It stops short of saying outright 'use search_docs first to find a URL,' but the routing is clear.

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.