scdo-agent-plugins

Overview Schema Source Related Servers Discussions Admin

Invite info

invite_info

Read-only

Fetch invite programme status including contract, limits, and live state, and retrieve the invite link for a given Shard0 address.

Instructions

Invite programme status (contract, limits, live) and, given a Shard0 address, that address's invite link.

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": "invite_info"
  }
}

Input Schema

Name	Required	Description	Default
`address`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered elsewhere. The description adds value by disclosing the conditional behavior (address yields that address's link) and the fields of the programme status, but says nothing about auth requirements, rate limits, or failure modes for an invalid/off-chain address.

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 dense sentence, front-loading the always-available programme status before the conditional address-dependent link. No filler sentences and no wasted clauses.

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?

With no output schema, the description must describe return values, and it does enumerate the key programme-status fields (contract, limits, live) plus the invite link. However it leaves the link's format, the meaning of the status fields, and the address-format requirement unexplained, so it is adequate but not complete.

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 carry the parameter's meaning. It partially does: it tells the agent the value must be a Shard0 address and implies the parameter is optional (programme status is returned regardless). It does not specify address format or encoding, so the gap is only partly closed.

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 resource (invite programme) and enumerates what it returns: programme status carried by the fields contract, limits, and live, plus a per-address invite link. The verb is implicit ('info'/'status') but the effect is unambiguous, and no sibling tool competes for this niche.

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 explicit when-to-use or when-not-to-use guidance. The description implies you call it to inspect invite-programme state or retrieve a specific address's invite link, but it never states conditions, prerequisites, or alternatives among the many sibling tools.

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