Skip to main content
Glama

Sjothr company tokenization and fundraising

One Sjothr campaign

sjothr_campaign
Read-onlyIdempotent

Public record of one Sjothr campaign by campaign id: token, vault, funding goal, capital raised, deadline, state and dossier reference.

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": {
      "campaignId": "<campaignId>"
    },
    "name": "sjothr_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.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, open-world. The description contributes real context beyond them: 'Public record' signals no authentication or ownership scoping is required, and the field list discloses what the read actually returns in the absence of an output schema. It omits error behavior for a nonexistent id.

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 sentence, front-loaded with the identifying clause then the payload fields; nothing is padded. The field enumeration is dense but earns its place because no output schema exists.

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 one-parameter read tool, the description plus annotations cover safety, access model (public), and return contents. Remaining gaps are minor: no note on what happens for an invalid or unknown campaign id, and no indication of the response's structure.

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%, but the single parameter's pattern (^0x[0-9a-fA-F]{64}$) machine-documents that it is a bytes32-style hex identifier, and the description confirms it identifies a campaign. The description adds no further meaning such as where the id comes from or what an unknown id does, so it neither compensates fully nor is it empty.

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-object: a public record of ONE Sjothr campaign retrieved by campaign id, and enumerates the payload (token, vault, funding goal, capital raised, deadline, state, dossier). The singular 'one campaign' implicitly distinguishes it from the plural sibling sjothr_campaigns, though that sibling is never named.

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?

'By campaign id' weakly implies you need an id in hand, but there is no explicit when-to-use, no when-not-to-use, and no pointer to sjothr_campaigns for enumeration versus this single-record lookup. The agent must infer the routing itself.

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.