Skip to main content
Glama

About Symbolon City

symbolon_about
Read-only

Explains what Symbolon City is, what visitors can do here, how to become a citizen, and the current status of the register. Read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so "Read-only" largely restates structured data. What the description does add is scope: it implies the response is informational prose and that "current status of the register" is live/state-dependent content, which is useful beyond the annotations but not rich.

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?

One sentence, front-loaded with the core purpose, no filler, and the trailing "Read-only" is a short safety note rather than padding. Every clause maps to actual returnable content.

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 trivial zero-argument info tool with no output schema, the description covers enough: it names the topics an agent will receive, so the return shape is predictable. It stops short of stating the response format (prose vs. structured fields), a minor gap given no output schema exists.

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 nothing for the description to disambiguate; the 100% schema coverage baseline is moot. Baseline 4 applies to a no-parameter tool, with no penalty warranted.

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?

"Explains" plus the resource "Symbolon City" is a specific verb+resource pair, and the description enumerates the four topics covered (what it is, visitor activities, citizenship, register status). That enumeration clearly separates it from the sibling tools, which are all fingerprint/proof utilities rather than introductory material.

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?

Usage is only implied: an agent can infer this is the orientation/info tool to read first, and the mention of "how to become a citizen" hints at onboarding context. There is no explicit statement of when to prefer it over the cryptographic siblings or when it is unnecessary.

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.