Skip to main content
Glama
Sign In

Marvnor

by io.github.wendelxia
OverviewDiscussionsAdmin

recall

Read-onlyIdempotent

source OR text: verified records keyed by record_id OR question search (not exhaustive). {}: connection. Pages: complete/next_cursor.

Input Schema

NameRequiredDescriptionDefault
textNoQuestion; known entity: use source.
limitNotext: 1-20 (default 12); source: 1-100 (default 20).
cursorNosource: next_cursor; keep filters.
schemaNoParameters: tool name, compute, computations, rules, proof, proofs, capabilities.
sourceNoExact saved entity/project name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Source mode: next_cursor; keep filters unchanged."New value: +"source: next_cursor; keep filters."
    • changedInput schema / properties / schema / description
      Previous value: -"Full parameters: tool name, compute, computations, rules, proof, proofs, capabilities."New value: +"Parameters: tool name, compute, computations, rules, proof, proofs, capabilities."
    • changedInput schema / properties / source / description
      Previous value: -"Exact saved entity/project name; lists its records."New value: +"Exact saved entity/project name."
    • changedInput schema / properties / text / description
      Previous value: -"Full question to search; for a known entity use source."New value: +"Question; known entity: use source."
  2. Changed9 schema fields changed
    • addedInput schema / oneOf
      Added value: +[
+  {
+    "maxProperties": 0
+  },
+  {
+    "required": [
+      "text"
+    ]
+  },
+  {
+    "required": [
+      "source"
+    ]
+  },
+  {
+    "required": [
+      "schema"
+    ]
+  }
+]
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Source mode: next_cursor; keep filters unchanged.",
+  "type": "string"
+}
    • removedInput schema / properties / limit / default
      Removed value: -12
    • addedInput schema / properties / limit / description
      Added value: +"text: 1-20 (default 12); source: 1-100 (default 20)."
    • changedInput schema / properties / limit / maximum
      Previous value: -20New value: +100
    • addedInput schema / properties / schema
      Added value: +{
+  "description": "Full parameters: tool name, compute, computations, rules, proof, proofs, capabilities.",
+  "type": "string"
+}
    • addedInput schema / properties / source
      Added value: +{
+  "description": "Exact saved entity/project name; lists its records.",
+  "type": "string"
+}
    • addedInput schema / properties / text / description
      Added value: +"Full question to search; for a known entity use source."
    • changedInput schema / required
      Previous value: -[
-  "text"
-]New value: +[]
  3. Changed9 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
    • removedInput schema / properties / as_of
      Removed value: -{
-  "maxLength": 100,
-  "minLength": 1,
-  "type": "string"
-}
    • removedInput schema / properties / context
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "domain_id": {
-      "maxLength": 200,
-      "minLength": 1,
-      "type": "string"
-    },
-    "qualifiers": {
-      "description": "Conditions: JSON scalars/lists, no nested objects.",
-      "maxProperties": 64,
-      "type": "object"
-    },
-    "scope": {
-      "maxLength": 200,
-      "minLength": 1,
-      "type": "string"
-    },
-    "subdomain_id": {
-      "maxLength": 200,
-      "minLength": 1,
-      "type": "string"
-    },
-    "subject_version": {
-      "maxLength": 200,
-      "minLength": 1,
-      "type": "string"
-    }
-  },
-  "required": [],
-  "type": "object"
-}
    • removedInput schema / properties / facets
      Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "as_of": {
-        "maxLength": 100,
-        "minLength": 1,
-        "type": "string"
-      },
-      "context": {
-        "additionalProperties": false,
-        "properties": {
-          "domain_id": {
-            "maxLength": 200,
-            "minLength": 1,
-            "type": "string"
-          },
-          "qualifiers": {
-            "description": "Conditions: JSON scalars/lists, no nested objects.",
-            "maxProperties": 64,
-            "type": "object"
-          },
-          "scope": {
-            "maxLength": 200,
-            "minLength": 1,
-            "type": "string"
-          },
-          "subdomain_id": {
-            "maxLength": 200,
-            "minLength": 1,
-            "type": "string"
-          },
-          "subject_version": {
-            "maxLength": 200,
-            "minLength": 1,
-            "type": "string"
-          }
-        },
-        "required": [],
-        "type": "object"
-      },
-      "source_kind": {
-        "maxLength": 80,
-        "minLength": 1,
-        "type": "string"
-      },
-      "target_kind": {
-        "maxLength": 80,
-        "minLength": 1,
-        "type": "string"
-      },
-      "text": {
-        "maxLength": 2000,
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "required": [
-      "text"
-    ],
-    "type": "object"
-  },
-  "maxItems": 8,
-  "minItems": 1,
-  "type": "array"
-}
    • removedInput schema / properties / include_source_context
      Removed value: -{
-  "default": false,
-  "description": "Include attributed excerpts, not full history.",
-  "type": "boolean"
-}
    • removedInput schema / properties / source_kind
      Removed value: -{
-  "maxLength": 80,
-  "minLength": 1,
-  "type": "string"
-}
    • removedInput schema / properties / target_kind
      Removed value: -{
-  "maxLength": 80,
-  "minLength": 1,
-  "type": "string"
-}
    • removedInput schema / properties / text / maxLength
      Removed value: -2000
    • removedInput schema / properties / text / minLength
      Removed value: -1
  4. Changed7 schema fields changed
    • changedInput schema / properties / context / properties / qualifiers / description
      Previous value: -"Conditions accepted by normalize_context: JSON scalars or lists, no nested objects."New value: +"Conditions: JSON scalars/lists, no nested objects."
    • changedInput schema / properties / facets / items / properties / context / properties / qualifiers / description
      Previous value: -"Conditions accepted by normalize_context: JSON scalars or lists, no nested objects."New value: +"Conditions: JSON scalars/lists, no nested objects."
    • addedInput schema / properties / facets / items / properties / source_kind
      Added value: +{
+  "maxLength": 80,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / facets / items / properties / target_kind
      Added value: +{
+  "maxLength": 80,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / include_source_context
      Added value: +{
+  "default": false,
+  "description": "Include attributed excerpts, not full history.",
+  "type": "boolean"
+}
    • addedInput schema / properties / source_kind
      Added value: +{
+  "maxLength": 80,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / target_kind
      Added value: +{
+  "maxLength": 80,
+  "minLength": 1,
+  "type": "string"
+}
  5. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful behavioral context that question search is not exhaustive and that results are paginated via 'complete/next_cursor', but '{}: connection' is cryptic and no return shape or permission context is given.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short and somewhat front-loaded around the source/text distinction. However, the fragment '{}: connection.' is unexplained and does not earn its place, making the structure less useful than a clean two-sentence statement would be.

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?

This is a complex retrieval tool with a oneOf schema, five parameters, and no output schema, so the description should clarify return values and mode selection more fully. It mentions paging but does not explain record shape, what the empty-object mode returns, or how the schema mode differs from source/text; '{}: connection' is insufficient for an agent to predict the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all five parameters in detail. The description adds only high-level mode language ('source OR text', record_id keying, question search) and pagination wording, without explaining limits, cursor retention, or the schema mode beyond what the schema already says.

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 a resource ('verified records') and two access modes ('source' keyed by record_id, and 'text' question search), but it never states the verb explicitly and the phrase '{}: connection' is opaque. It does not distinguish the tool from siblings such as verify or correct_fact, leaving the agent to infer that this is a retrieval operation from the name 'recall'.

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 gives only the terse 'source OR text' distinction and '(not exhaustive)' caveat. It provides no explicit guidance on when to use recall versus siblings like verify, correct_fact, forget_facts, or remember_facts, and no prerequisites or exclusions are stated.

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

All Marvnor toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources