Skip to main content
Glama

Principal Reputation for Agents

get_standing

Published standing class + publication state

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

Input Schema

NameRequiredDescriptionDefault
principal_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.7/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full disclosure burden, yet it says nothing about read-only nature, auth requirements, or error behavior. The phrase 'publication state' weakly implies a read of a status value, which is the only behavioral hint present.

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

Conciseness2/5

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

It is very short, but this is under-specification rather than conciseness: a single fragment with no front-loaded statement of what the tool does or returns.

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

Completeness1/5

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

For a tool with an undocumented parameter, no annotations, no output schema, and a near-identical sibling (check_standing), the description omits everything an agent needs: the action, the parameter meaning, return semantics, and sibling selection criteria.

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 coverage is 0%, so the description must explain principal_id and it does not mention it at all — no indication of whose standing is fetched or whether omitting it is meaningful despite the parameter being optional.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a bare noun phrase ('Published standing class + publication state') with no verb or resource framing, so it largely restates the tool name rather than explaining what get_standing does. It hints at the returned fields but never states the action (retrieval) or its scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool, and critically no differentiation from the sibling check_standing, which is the most obvious alternative an agent would weigh. Nothing indicates prerequisites or exclusions.

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