Mirsad

current_fact

Fetch the currently valid value for a subject and predicate with provenance to answer fact queries from a shared AI memory hub.

Instructions

The currently valid value for subject+predicate, with provenance.

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": {
      "subject": "<subject>",
      "predicate": "<predicate>"
    },
    "name": "current_fact"
  }
}

Input Schema

Name	Required	Description	Default
`subject`	Yes
`predicate`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

C2.4/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, yet it never states whether this is a read-only lookup, what happens when no fact exists (null? empty? error?), or how 'currently valid' is determined when conflicts are open. 'With provenance' hints at returned metadata but does not explain its shape, even though an output schema exists to cover details.

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 zero padding, which is structurally clean. However, the terseness crosses into under-specification for a tool with no annotations and undocumented parameters.

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 excuses it from describing return values, but with no annotations and 0% parameter coverage the description should say more about lookup semantics and failure modes. For a two-required-parameter retrieval tool in a memory system with conflict tools, this leaves key questions unanswered.

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 needed to explain the two parameters and did not. Saying 'subject+predicate' only restates that both are required together; it gives no format, canonicalization, or alias-handling guidance (notably whether aliases registered via add_alias resolve here).

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 phrase 'The currently valid value for subject+predicate, with provenance' identifies the resource and its key fields, but uses no verb, so the agent must infer that this is a read/lookup operation rather than a mutation. It also gives no hint of how it differs from siblings like recall or why, which likely also return facts.

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 at all: nothing says whether to call this before or instead of recall, timeline, or why, and no preconditions are stated. The mention of 'currently valid' faintly implies use when conflicts may exist, but that is inference rather than guidance.

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

Deploy Server