Skip to main content
Glama
Sign In
agent-reasoning-mcp

agent-reasoning-mcp

by putervision
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gate_intention

Read-onlyIdempotent

Evaluate an intention's safety and risk before dispatching to behavior-mcp; approve or reject it and issue an HMAC dispatch token if approved.

Instructions

Evaluate an intention before dispatching to behavior-mcp and issue a cryptographic HMAC dispatch token if approved. Use gate_intention instead of manage_intentions when verifying precondition safety and issuing execution authorization rather than tracking intention state.

Returns gate verdict (approved/rejected), risk evaluation, and HMAC dispatch token.

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": {
      "project": "<project>",
      "proposed_action": "<proposed_action>"
    },
    "name": "gate_intention"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesTarget project slug
state_packNoOptional explicit StatePack
intention_idNoTarget intention ID
context_goal_idNoActive goal being pursued
proposed_actionYesProposed behavior action to execute

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), and the description adds real context beyond them: this is a precondition gate whose approval produces a cryptographic HMAC token, and it returns a verdict plus risk evaluation. It stops short of saying what a rejection looks like to the caller or whether the token has a lifetime/one-time-use constraint, so it is not fully transparent.

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?

Three sentences, roughly fifty words, with the core purpose front-loaded in the first clause and no filler. The return-value sentence earns its place because no output schema exists.

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?

With no output schema, the description carries the return-value burden and does so adequately (verdict, risk evaluation, HMAC token). Given a five-parameter nested schema and a gating role in a behavior-dispatch pipeline, it could say more about rejection handling and token use, but nothing essential to calling it correctly is missing.

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 all five parameters (project, state_pack, intention_id, context_goal_id, proposed_action and its nested fields) are already documented structurally. The description references the intention and proposed action conceptually but adds no syntax, format, or interaction detail beyond the schema, which is the baseline-3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Evaluate an intention before dispatching to behavior-mcp') plus the concrete output ('issue a cryptographic HMAC dispatch token if approved'). It also explicitly names the sibling it is not, manage_intentions, so an agent can separate the two without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit routing rule: 'Use gate_intention instead of manage_intentions when verifying precondition safety and issuing execution authorization rather than tracking intention state.' This names the alternative and the condition that selects it, which is exactly the when/when-not guidance an agent needs.

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

Deploy Server

Other Tools