Skip to main content
Glama

Sjothr company tokenization and fundraising

Fetch a Sjothr campaign or guide

fetch
Read-onlyIdempotent

Full record of one Sjothr campaign or full text of one guide, by id (from search).

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
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered by structured data. The description adds only that the return is a 'full record' or 'full text', with no mention of size limits, truncation, or not-found behavior. With annotations carrying most of the burden, this is adequate but thin.

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?

A single sentence with no filler, and the resource scope is front-loaded before the id provenance hint. The phrase 'one Sjothr campaign or full text of one guide' is slightly dense but each clause carries information.

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?

This is a low-complexity single-parameter read tool with full annotation coverage, so the description is close to sufficient, and it does sketch the return value in the absence of an output schema. The unresolved question of how the campaign/guide union is determined and what a not-found result looks like keeps it at a minimum-viable level.

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 0% for the single id parameter, so the description carries the burden, and it does contribute one useful fact: the id originates from 'search'. It still does not state the id's format (string shape, campaign vs guide id distinction) or what happens with an invalid or wrong-type id, so it only partly compensates.

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 ('Full record of', 'full text of') and a specific resource (one Sjothr campaign or one guide), keyed by id. This clearly contrasts with the sibling 'search', which produces ids rather than full documents. It stops short of naming the sibling explicitly, but the distinction is inferable.

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

Usage Guidelines3/5

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

The parenthetical '(from search)' does route the agent to the sibling that supplies the id, which is genuine usage guidance. However, there is no statement of when not to use it, and no clarification of how the campaign-vs-guide branch is chosen (one shared id namespace, or does the caller need to know the type in advance?).

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.