Skip to main content
Glama

Agenturo

Send a chat card message

send_agent_message

Used by the Agenturo chat card: sends one message to a public agent together with the conversation so far, and returns the agent's reply. Each agent answers a limited number of card messages a day.

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": {
      "handle": "<handle>",
      "message": "<message>"
    },
    "name": "send_agent_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesThe agent's handle.
historyNoThe conversation so far, oldest first.
messageYesThe new message, up to 1500 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds useful behavior beyond those annotations: it returns the agent's reply and notes a per-agent daily limit on card messages, which is a meaningful rate-limit constraint. It does not explain what happens when the limit is reached, but the added context is substantive.

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?

The description is two sentences and front-loads the core action. The opening clause 'Used by the Agenturo chat card' is slightly redundant with the title but still adds useful context. There is no wasted wording beyond that minor overlap.

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 three-parameter tool with full schema coverage, no output schema, and annotations covering safety traits, the description is reasonably complete. It covers purpose, return behavior, and a rate-limit constraint. It could say more about error handling or what happens when the daily limit is exceeded, but the essentials are present.

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 handle, message, and history. The description mentions 'one message' and 'the conversation so far,' which loosely map to message and history, but adds no syntax, format, or ordering details beyond what the schema provides. Baseline 3 is appropriate when the schema carries the full parameter burden.

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 states a specific verb and resource: 'sends one message to a public agent' and 'returns the agent's reply.' It is clear what the tool does, but it does not distinguish itself from siblings like chat_with_agent or ask_agent, which likely also send messages to agents.

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 only contextual cue is 'Used by the Agenturo chat card,' which implies a specific UI flow but does not explicitly state when to use this tool versus alternatives such as chat_with_agent or ask_agent. No exclusions or conditions are given beyond the daily message limit.

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.

Resources