Skip to main content
Glama

Explain the rules

explain_rules

Returns the precedence rules, network plane definitions, confidence states, and RTT falsifier that govern all fleet-geo location results, so you can interpret evidence and contradictions consistently.

Instructions

Return the source precedence, plane definitions, confidence states and the RTT falsifier used by every other tool.

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_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It makes clear this is a zero-argument reference lookup with no side effects implied, which is the main behavioral fact an agent needs. It does not say whether the content is static or version-dependent, nor how large the response is, so meaningful disclosure gaps remain.

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 sentence with no filler, front-loading the verb and then the four content categories. Every clause names a distinct returned artifact, so nothing is wasted.

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?

With no output schema, the description must carry the return-value burden, and it does so by enumerating the four categories of content returned. For a zero-parameter reference tool that is close to sufficient; a note on whether the content is static would close the remaining gap.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The enumerated return categories are not parameters, so they add no schema-level meaning beyond confirming the tool is argument-free.

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?

"Return" plus a concrete enumeration of the four things returned (source precedence, plane definitions, confidence states, RTT falsifier) tells an agent exactly what this tool yields. The clause "used by every other tool" also signals that this is the shared reference/glossary tool rather than a data-fetching sibling. It stops short of naming a specific sibling to prefer or avoid, which keeps it out of the top band.

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?

The phrase "used by every other tool" implies this is the reference an agent should consult to interpret outputs from siblings, which is genuine implied guidance. However, there is no explicit "call this before/after X" instruction, no statement of when it is unnecessary, and no named alternative. Usage is inferable but not stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.