Skip to main content
Glama

Sjothr company tokenization and fundraising

How a Sjothr raise works

sjothr_rules
Read-onlyIdempotent

Rules of a Sjothr raise: who pays which fee, how capital is released in stages by token-holder votes, when backers are refunded, and the risks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sjothr_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds useful scope information by naming the specific topics covered (fees, staged release via votes, refunds, risks), but says nothing about form or stability of the content — whether it is static documentation open to change, or whether it varies per campaign.

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 that front-loads the domain ('Rules of a Sjothr raise') and then lists the covered areas, with no filler. It is appropriately sized for a zero-parameter documentation tool, though the opening could have been anchored with an explicit verb.

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 zero-parameter, read-only reference tool with no output schema, the description covers the subject matter adequately. It leaves open whether the content is generic across all Sjothr raises or tied to a specific campaign, and gives no hint about output format or length, which matters given openWorldHint=true.

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?

The tool takes zero parameters and the schema is an empty object with additionalProperties=false, so there is nothing for the description to disambiguate. The baseline for a parameterless tool applies, with no missing parameter meaning.

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

Purpose3/5

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

The description enumerates the subject matter ('who pays which fee, how capital is released in stages by token-holder votes, when backers are refunded, and the risks'), so the topic is clear. But it is a noun phrase with no verb, and 'Rules' is ambiguous — it could read as policy constraints the agent must obey rather than a reference document about how raises work. It does not explicitly state that this returns explanatory content about raise mechanics rather than campaign data.

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 on when to consult this versus the sibling tools (sjothr_campaign, sjothr_campaigns, fetch, search). An agent must infer that this is background reading before or instead of performing a campaign lookup; nothing states that explicitly, and no exclusions are given.

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.