Skip to main content
Glama

Monte statistics

Search the glossary

search_terms
Read-onlyIdempotent

Statistics terms in plain English with an example each, matched on the term or its meaning.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA word or phrase, like standard error or p-value

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description need not repeat them. It contributes real behavioral context beyond them: each result carries a plain-English definition plus an example, and retrieval is semantic as well as lexical, which shapes how an agent should query and what to expect back. It says nothing about no-match behavior or result ranking.

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?

A single front-loaded sentence that packs the resource, the result shape, and the matching rule with no filler. Nothing is redundant with the title or schema.

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 one-parameter read tool with full schema coverage and a rich annotation set, the description supplies everything essential: what is returned and how matching works. Only minor gaps remain, such as empty-result behavior and whether multiple matches come back.

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

Parameters3/5

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

The schema documents its single parameter at full coverage, so a baseline 3 applies. The description does add one useful nuance, that matching happens on meaning as well as literal term, which tells the agent it can query a concept rather than an exact string, but it offers no guidance on phrasing, casing, or partial matches.

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?

States the resource clearly: statistics terms rendered in plain English, each with an example, and discloses the matching strategy (term or meaning). It stops short of naming how this differs from siblings such as get_topic or list_topics, so an agent must infer the glossary-vs-topic boundary.

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 rather than stated: an agent can infer you call it to resolve a statistics term or concept into a plain-English explanation. There is no explicit when-to-use, no exclusion, and no pointer to alternatives such as get_topic for topic-level content.

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