Skip to main content
Glama

Trust levels

trust_levels
Read-onlyIdempotent

How review labels are computed, how completed-job counts work, and what this door does not do. Read only. Does not take an order or a payment.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description restates "Read only" (redundant) but does add useful scoping context by ruling out order-taking and payments, clarifying it is purely informational. It says nothing about whether output is static reference text or dynamic, which would have been genuinely additive.

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?

Two short sentences, front-loaded with the subject matter followed by the read-only/scope caveat; there is no padding. The phrase "what this door does not do" is vague figurative language that costs a little clarity, but the overall size is appropriate for the tool's simplicity.

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 reference tool, the description covers the topic and the non-transactional boundary, which is close to sufficient. With no output schema present, though, the agent is left guessing the return format (prose explanation? structured label tiers?), and the odd "door" phrasing leaves the scope partly ambiguous.

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 meaning for the description to supply; the baseline applies. Nothing in the schema is left undocumented because the schema is empty.

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?

The description identifies the topic (how review labels are computed, how completed-job counts work) but never states what the tool actually returns or does — explain, document, list rules? It also distinguishes itself only through negation ("does not take an order or a payment") rather than by naming a sibling or a positive action. An agent gets the subject area but not a crisp verb+resource statement.

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 implied by the topic (read this to understand how trust/review labels and job counts are derived) and by the exclusion "does not take an order or a payment," which steers agents away from transactional use. However, there is no explicit when-to-use trigger, no statement of prerequisites, and no named alternative among siblings such as operating_rules or phoenix_about.

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