Skip to main content
Glama

list_facts

Retrieve trusted facts filtered by category, minimum trust score, and result limit to supply reliable context for agents.

Instructions

List high-trust facts filtered by optional category.

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
limitNo
categoryNo
min_trustNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and does little: 'high-trust' gestures at a trust threshold but never states the default (0.5), the default result cap (30), ordering, or pagination behavior. It does not clarify whether results are truncated silently or what happens when the category matches nothing.

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 front-loaded sentence with no filler, which reads cleanly. It is arguably under-specified rather than overly long, but as a structural matter there is no wasted wording.

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?

An output schema exists, so return values need not be explained, but for a three-parameter tool with zero schema coverage and no annotations the description is too thin. The agent cannot determine how limit interacts with the trust filter or what units min_trust uses.

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, but it only echoes 'category' and obliquely references min_trust via 'high-trust.' The limit parameter, the numeric type/range of min_trust, and the meaning of an empty category string (default "") are all undocumented anywhere.

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 a specific verb and resource ('List ... facts') plus a filter qualifier ('filtered by optional category'), so the agent knows this is a filtered listing operation. It does not, however, distinguish itself from the sibling search_facts or get_fact, leaving the agent to infer that this is the enumeration path versus lookup or search.

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?

The description offers no when-to-use guidance, no exclusions, and never names an alternative. The only hint at usage is 'optional category,' and the agent is left to guess whether this or search_facts should be called for a given retrieval need.

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