Skip to main content
Glama

dislop

dislop_explain

Explain a dislop rule with check question and examples (0 credits).

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": {
      "ruleId": "<ruleId>"
    },
    "name": "dislop_explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
ruleIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the cost (0 credits) and the shape of the response (check question and examples), which is genuinely useful, but it says nothing about whether the call is read-only, whether ruleId must exist, what happens on an unknown ID, or whether output is localized.

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?

A single compact sentence with the resource and payoff front-loaded and no filler. It is arguably too terse for the two undocumented parameters, but as conciseness it holds up well.

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

Completeness2/5

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

With no annotations, no output schema, and 0% schema coverage on two parameters, the description leaves material gaps: parameter meanings, behavior for invalid ruleIds, and whether the explanation is localized. It covers purpose and cost but not enough for confident invocation.

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 description coverage is 0%, so the description must compensate and does not. "ruleId" is only obliquely implied by "a dislop rule," and "lang" is never mentioned, leaving the zh/en enum and its default or effect on output entirely unexplained.

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?

A concrete verb ("Explain") and resource ("a dislop rule") plus the returned content (check question and examples) make the purpose clear, and it is distinguishable from action-oriented siblings like dislop_check or dislop_deslop. It stops short of naming any sibling explicitly, so the differentiation is inferred rather than stated.

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?

Use is only implied: an agent can infer this is the tool for understanding a rule before applying it elsewhere. The "(0 credits)" note is a useful selection signal, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative for actually testing a rule.

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.