Skip to main content
Glama
Sign In

Memro

by co.memro.mcp
OverviewDiscussionsAdmin

log_intent

Declare your non-blocking intention for a resource (shared with agents in the same account/space).

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": {
      "resource": "<resource>",
      "intent": "<intent>"
    },
    "name": "log_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttlNoIntent duration in seconds (default 900, max 7200)
intentYes
resourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Since no annotations are provided, the description must carry the burden of behavioral disclosure. It successfully communicates the key behavioral trait of being 'non-blocking' and 'shared,' which is essential state information. It does not disclose failure modes or API constraints beyond the schema.

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 highly effective, packing the action, the nature of the operation (non-blocking), and the environment (shared with agents) into a single, dense, and informative sentence. Every word contributes meaningful operational context.

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 state logging tool, the definition is quite complete as it explains the scope and nature of the recorded data. It provides all necessary high-level context regarding data sharing and operational constraints required for an agent to make an initial decision.

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

Parameters4/5

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

Given the low schema coverage (33%), the description is highly valuable for defining the `ttl` parameter. It clarifies that the value represents the 'Intent duration in seconds' and specifies critical operational bounds, including the default and maximum allowed duration.

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 clearly identifies the action (declare) and the target (intent for a resource). By specifying 'non-blocking,' it adds an important operational constraint to the purpose of the logging action. While clear, it lacks a definitive statement on why this logging is required over other memory tools.

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?

The tool provides crucial contextual guidance by stating that the intent is 'shared with agents in the same account/space.' This defines its collaborative nature. However, it offers no explicit instructions on when to use this tool versus another potential mechanism for state management.

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

All Memro toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources