Skip to main content
Glama

list_facts

Retrieves the facts, skills, and blocked phrases the checker uses to verify AI-written documents for accuracy and context.

Instructions

The facts, skills and blocked phrases the checker uses.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no statement that this is a read-only, side-effect-free retrieval, no mention of whether the data is static configuration or dynamically computed, and no auth or scope notes. The only hint of behavior is the word 'checker', which implies configuration data but is not explained.

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?

It is a single short fragment with zero filler, and the key content ('facts, skills and blocked phrases') is front-loaded. It loses a point for being a sentence fragment that omits the action verb, making it read as a label rather than an instruction.

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?

Because an output schema exists, the description needn't explain return values, and with zero parameters there is little surface area to cover. Still, for a tool an agent must choose deliberately, it omits why or when to call it and how it relates to 'check_document', leaving a real contextual 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, so the baseline applies and there is nothing parameter-related the description needed to compensate for. The schema is empty and consistent with the no-argument nature of the call.

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 names the resource contents ('facts, skills and blocked phrases the checker uses'), which goes beyond a bare restatement of the name, but it is a noun phrase with no verb and never states that it returns/lists anything. It also does nothing to distinguish itself from the sibling 'check_document', so the agent must infer the retrieval action from the tool name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of prerequisites, and no indication of how this differs from 'check_document'. The agent is left to guess the context in which listing checker facts is appropriate.

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

Deploy Server

Other Tools