Skip to main content
Glama

Agenturo

Chat with an agent

chat_with_agent
Read-onlyIdempotent

Open a chat with one public Agenturo agent inside this conversation. Where the host shows interactive cards, the user talks to the agent there directly and sees its replies in its own words; elsewhere this returns the agent's profile. Agents whose owners keep them to their own page show a link to it instead.

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>"
    },
    "name": "chat_with_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesThe agent's handle, for example "anton" for anton.agenturo.app. A full address or URL also works.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare safety (readOnly, idempotent, non-destructive, closed-world); the description adds real outcome branching that annotations cannot express — inline card chat with the agent's own words, versus a returned profile, versus a redirect link for page-locked agents. It doesn't say whether the chat is persisted or how a conversation is resumed, but the main behavioral variance is disclosed. Mild tension with openWorldHint=false given that arbitrary full URLs are accepted, though this is not a clear contradiction.

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?

Three sentences, front-loaded with the action and then the outcome branches. Dense but each clause carries distinct information; the semicolon-separated structure is slightly awkward but not wasteful.

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 single-parameter tool with rich annotations and no output schema, the description covers what the agent gets back in each of the three modes. Only gap is what a returned 'profile' contains, though that is arguably beyond the description's remit.

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?

One required parameter with 100% schema description coverage, so the schema already explains the handle format and that a full address works. The description adds nothing further about the handle, which is the correct baseline when the schema does the work.

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: 'Open a chat with one public Agenturo agent inside this conversation.' The scoping word 'one public' plus 'inside this conversation' separates it from a general find/discovery call, though it never names which sibling to use instead (ask_agent, send_agent_message).

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?

Usage is only implied through the described behavior branches: interactive-card hosts chat inline, owner-restricted agents yield a link, and everything else returns a profile. There is no explicit 'use this when / don't use this when' statement, and the sibling tools ask_agent and send_agent_message are never referenced as alternatives.

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