Skip to main content
Glama

get_fact

Fetch complete metadata and content for a single fact by fact_id to access stored knowledge from shared SQLite memory.

Instructions

Fetch full metadata and content for a single fact by fact_id.

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

Input Schema

NameRequiredDescriptionDefault
fact_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/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. It says the tool fetches full metadata and content, but does not disclose read-only safety, permission requirements, not-found behavior, or rate limits; the output schema covers return shape but not these behavioral traits.

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?

The description is a single front-loaded sentence with no unnecessary wording. Every part contributes to identifying the operation and its scope.

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?

For a simple one-parameter getter with an output schema, the description is adequate but incomplete. It covers what is returned at a high level, yet leaves gaps in usage guidance and fact_id semantics that matter for correct 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?

The only parameter, fact_id, is mentioned but not explained beyond the schema's integer type. With 0% schema description coverage, the description should clarify what a fact_id represents or its expected format, but it adds no meaning beyond the parameter name.

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?

The description states a specific verb ("Fetch"), resource ("fact"), and scope ("single fact by fact_id"). It does not explicitly name or differentiate from siblings like search_facts or list_facts, but the single-by-id scope makes the purpose clear.

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 implied: call this when you have a fact_id and need full details for that fact. There is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative for cases where the id is unknown.

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