Skip to main content
Glama

Sjothr fundraising campaigns

sjothr_campaigns
Read-onlyIdempotent

Retrieve public fundraising campaign details on Base, including token, status, USDC funding goal and raised capital, deadline, and public record page for campaign due diligence.

Instructions

Public fundraising campaigns on Sjothr: company token, state, funding goal and capital raised in USDC, deadline and public record page.

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_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond that by stating the records are public-only, denominated in USDC, and include a public record page — behavioral context not present in structured fields. It remains silent on result ordering, size, or truncation for a listing operation.

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 compact sentence with the resource front-loaded and the field inventory after the colon; nothing is redundant. It reads as a noun phrase rather than an action statement, which slightly weakens the opening.

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 listing tool the description covers the resource and the returned fields, which substitutes for the missing output schema. It omits any statement of result volume, ordering, or the relationship to the singular sjothr_campaign sibling, so an agent must guess at scoping.

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, so there is no parameter semantics to explain and the baseline of 4 applies. The field list in the description instead documents the response shape, which is useful given there is no output schema.

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?

The description identifies a specific resource (public fundraising campaigns on Sjothr) and enumerates the fields each record carries, so an agent knows what a call yields. It stops short of an explicit verb ('list') and never contrasts itself with the singular sibling sjothr_campaign, leaving disambiguation to inference.

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 when-to-use guidance: nothing says this is the bulk/listing counterpart to sjothr_campaign, nor when an agent should prefer search or fetch instead. The word 'Public' implies a scope filter but is never stated as a usage condition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.