Skip to main content
Glama
Sign In

factstable

by com.factstable
OverviewDiscussionsAdmin

motuk_get_fact

Get one verified fact from the motuk pack. Refuses (do_not_answer) when drifted or unverified — never guesses.

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": {
      "fact_id": "<fact_id>"
    },
    "name": "motuk_get_fact"
  }
}

Input Schema

NameRequiredDescriptionDefault
fact_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose a genuinely useful behavior: it returns a do_not_answer sentinel rather than guessing when a fact is drifted or unverified. It omits error behavior for an unknown fact_id and any auth/rate-limit notes, keeping it below a 5.

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?

Two short sentences, zero filler, with the retrieval purpose front-loaded and the refusal behavior second. Every clause carries information.

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?

No annotations and no output schema, so the description should cover return values and parameter provenance. It hints at the do_not_answer case but never describes a successful response or where fact_id comes from, leaving real gaps for a one-parameter lookup tool.

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 explain the single parameter — but it never says what fact_id is, its expected format, or that it should come from motuk_list_facts. It also says nothing about the returned payload shape.

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 ("Get one verified fact from the motuk pack") and the domain prefix in the name/description separates it from the ~30 sibling *_get_fact tools. It does not explicitly contrast with motuk_list_facts or motuk_changes, but the singular resource plus domain is unambiguous.

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 only implied: the agent learns this is the single-fact retrieval path, and that it may refuse. It never says when to prefer motuk_list_facts (to find a fact_id) or motuk_changes over this tool, and names no alternatives.

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

All factstable toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources