Skip to main content
Glama

Knowledge propose

knowledge_propose
Read-onlyIdempotent

Checks a durable instruction or a reusable request (shortcut) the person stated, against what Knowledge already holds. Saves nothing: returns the shortcut to save with knowledge_manage once the person says yes, or the link where they add an instruction.

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": {
      "input": "<input>"
    },
    "name": "knowledge_propose"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementNoRequired for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence.
idempotencyKeyNoRequired for mutations. Reuse the same key only when retrying the exact same call; a completed outcome is applied once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / input / properties / kind / enum
      Previous value: -[
      -  "instruction",
      -  "shortcut"
      -]New value: +[
      +  "instruction",
      +  "result",
      +  "shortcut"
      +]
    • changedInput schema / properties / userStatement / description
      Previous value: -"Required for launch_brief: the latest verbatim user request or free-text answer. Otherwise optional user-provided context, treated as an unverified user statement, never permission or verified platform evidence."New value: +"Required for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is known. The description adds real value beyond that by confirming the no-write guarantee ('Saves nothing') and describing what actually comes back — a shortcut to save later or a link to add an instruction — which matters since there is no output schema. It does not say what happens when the check finds a conflict or duplicate.

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?

Two sentences, no filler, with the identity of the tool front-loaded and the non-persistence + return behavior following. The second sentence is tightly packed but still readable and each clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, non-persisting tool with a nested input object and no output schema, the description covers purpose, the no-save guarantee, and the shape of the return value, which is enough to call it correctly. Gaps remain around conflict/duplicate handling and the undocumented 'result' kind and 'command' field.

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 75%, so the baseline is 3. The description hints at the kind values by naming 'instruction' and 'shortcut', but omits the third enum value 'result' and says nothing about the nested name, text, or command fields. It therefore adds only marginal meaning beyond the schema.

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: it checks a person-stated durable instruction or reusable shortcut against existing Knowledge, and explicitly says it saves nothing. That cleanly separates it from a saving/management tool. It loses a point because the referenced counterpart ('knowledge_manage') is not in the sibling list, and the abstract notion of 'Knowledge' is never grounded.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence effectively defines the workflow: call this first, then persist via knowledge_manage only after the person says yes, or hand them the link where they add an instruction. That tells an agent when to reach for this versus a write tool. It stops short of stating explicit exclusions, e.g. when not to propose at all.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.