Skip to main content
Glama

Sjothr company tokenization and fundraising

Search Sjothr

search
Read-onlyIdempotent

Search Sjothr campaigns and guides (tokenize a company, raise money for a startup, tokenized equity, milestone-based funding); returns ids for fetch.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior, so safety is covered. The description adds scope and the fact that results are ids for fetch, but it does not disclose result limits, ranking, matching behavior, or empty-result handling.

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?

A single compact sentence with the core action, resource scope, relevant examples, and return purpose front-loaded. There is no filler or repetition.

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-only search tool with rich annotations and no output schema, the description is nearly sufficient: it names the domain scope and explains that results are ids for fetch. The main missing pieces are query syntax and result/pagination behavior.

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 description coverage is 0%, so the description must compensate somewhat, and the parenthetical topic examples give useful hints about what the query can target. It still does not explain query syntax, matching rules, or whether the query searches names, text, or keywords.

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 and resource: searches Sjothr campaigns and guides, with domain examples and a clear return purpose (ids for fetch). It partially distinguishes itself from fetch, but does not explicitly clarify how it differs from sibling campaign-listing tools.

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?

Provides an implied usage flow by saying it returns ids for fetch, which helps the agent understand the search-then-fetch path. However, there is no explicit when-to-use guidance, no exclusions, and no comparison with alternatives such as sjothr_campaigns.

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.