Skip to main content
Glama

Explain the grading

explain_grading
Read-onlyIdempotent

Returns how the Portfolio Optimizer Pro grade works: the four factors and how each is scored, how they combine, every structural ceiling (cap) with its threshold, the A-range criteria, the letter bands, the risk reference bands, the data source, limitations and pricing. Takes no input.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
capsYes
factorsYes
pricingYes
summaryYes
disclaimerYes
data_sourceYes
grade_bandsYes
limitationsYes
combining_ruleYes
methodology_urlYes
a_range_criteriaYes
risk_reference_bandsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine context beyond that: it is a static reference payload with no input, and it discloses that the response includes limitations and pricing — non-obvious content that signals the tool is also a disclosure/caveat surface.

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?

One front-loaded sentence stating what is returned, followed by a compact enumeration of the payload's sections. It is long but not padded — each listed item names a distinct section of the response. A bulleted list would scan slightly better, and the trailing 'Takes no input' could lead rather than trail.

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

Completeness5/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, idempotent reference tool with an output schema, this is complete: the agent knows what it returns, that it takes no arguments, and that the payload includes limitations and pricing. Nothing needed to invoke it correctly is missing.

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?

There are zero parameters, so the baseline is 4. The description correctly and explicitly confirms 'Takes no input', which removes any ambiguity about how to invoke it, but adds nothing further since there is nothing to parameterize.

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?

The description uses a specific verb and resource ('Returns how the Portfolio Optimizer Pro grade works') and enumerates the exact content areas covered: factors, scoring, caps, thresholds, letter bands, risk bands, data source, limitations and pricing. An agent can tell this is a documentation/explanation tool rather than a scoring tool, though it never names the sibling grade_portfolio to make the contrast explicit.

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 by the purpose: an agent can infer it should call this when it needs to interpret or justify a grade. There is no explicit statement of when to use this instead of grade_portfolio, nor any exclusion or prerequisite guidance. 'Takes no input' is an invocation note, not usage guidance.

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