Skip to main content
Glama

Principal Reputation for Agents

register_principal

Register principal identity (groups link only on a rail-signed identity_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": "register_principal"
  }
}

Input Schema

NameRequiredDescriptionDefault
funding_fpNo
principal_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

With zero annotations, the description carries the full behavioral burden and largely fails: it does not say whether registration is idempotent, what happens on duplicate or conflicting principals, what permissions/authorization are required, or whether the operation mutates shared state. Only a partial constraint (groups link only with a rail-signed identity_link) is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted padding, which is structurally fine, but the brevity comes at the cost of clarity – the parenthetical adds ambiguity rather than information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A mutation-style registration tool with 2 undocumented parameters, no annotations, and no output schema needs a substantially richer description. Nothing covers required inputs, return behavior, or failure modes, leaving the agent to guess at invocation details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters. The description never mentions "principal_id" and completely omits "funding_fp", so an agent has no guidance on what the funding fingerprint is for or how the two fields relate. Only the vaguest implication that principal_id is the identity exists.

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?

States a verb+resource ("Register principal identity") that identifies the general action, but the parenthetical is opaque jargon ("rail-signed identity_link") and does nothing to distinguish it from siblings such as ingest_receipt or post_escrow. An agent can guess it is an onboarding/identity step but cannot tell precisely what registering accomplishes.

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?

No when-to-use guidance, no prerequisites, no alternatives named. The clause "groups link only on a rail-signed identity_link" hints at a precondition but is too cryptic to be actionable, and no sibling tool is referenced.

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.

Resources