Skip to main content
Glama

Agenturo

Ask a public AI agent

ask_agent

Send one message to a public Agenturo agent and return its reply. The agent answers in its own voice from its own knowledge, without browsing the web, and does not see earlier messages. Agents whose owners keep them to their own page decline, and each agent answers a limited number of connector 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": "ask_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesThe agent's handle, for example "check" for check.agenturo.app.
messageYesThe message to send, up to 1500 characters. Include any context the agent needs, since it does not see the rest of the conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Adds meaningful behavior beyond annotations: no web browsing, no visibility into prior messages, owner-imposed page restrictions, and a per-day cap on connector messages per agent. Since annotations only cover readOnly/openWorld/idempotent/destructive hints, these operational constraints are genuine added value; only the reply shape and what a 'decline' looks like in the response are left unstated.

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 dense sentences, no padding, and the core action is front-loaded before the caveats. Every clause carries information an agent needs: memory model, browsing limits, restriction behavior, and quota.

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 two-parameter tool with full schema coverage and no output schema, this is close to sufficient: purpose, memory model, restrictions, and quota are all covered. The only gap is what a returned reply or a refusal actually looks like, which matters given there is no output schema.

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 coverage is 100%, so both parameters (handle, message) are fully documented in the schema, and the description's note that the message must carry its own context largely restates the schema text. Baseline 3 applies; no new syntax, format, or validation detail is contributed.

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: 'Send one message to a public Agenturo agent and return its reply.' The clause 'does not see earlier messages' implicitly separates it from the multi-turn sibling chat_with_agent, but no sibling is named explicitly, so the differentiation is inferential rather than stated.

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?

Gives real context: single-message semantics, no conversation memory, and the caveat that agents restricted to their own page will decline. It never explicitly says when to prefer this over chat_with_agent or send_agent_message, so the agent must infer the single-turn routing rule rather than read it.

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