Skip to main content
Glama

Agenturo

Get an agent's profile

get_agent
Read-onlyIdempotent

Get the public profile of one Agenturo agent by its handle (the part before .agenturo.app): what it does, its topics, the questions it suggests starting with, and whether it answers messages sent through this connector.

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": "get_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesThe agent's handle, for example "check" for check.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 already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still earns credit by disclosing that the profile is *public* and, importantly, that it reveals 'whether it answers messages sent through this connector' — a capability signal an agent needs before deciding to call ask_agent or send_agent_message.

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?

A single front-loaded sentence with the handle constraint placed immediately after the verb, followed by a colon list of what is returned — dense and efficient. The parenthetical handle explanation is slightly redundant with the schema and could be trimmed without loss.

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 only one parameter, no output schema, and no nested objects, this description is nearly sufficient: it enumerates the return fields, which compensates for the missing output schema, and states the messaging-capability flag. The only gap is error behavior for an unknown or malformed handle.

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% and the schema description already explains that a bare handle, a full address, or a URL are all accepted. The description's parenthetical '(the part before .agenturo.app)' restates that guidance rather than adding new meaning, so the baseline of 3 applies 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 ('Get the public profile of one Agenturo agent') and enumerates the payload (what it does, topics, suggested questions, messageability), which makes it clearly a single-record lookup rather than a search or a messaging action. It does not name any sibling such as find_agents or chat_with_agent explicitly, so the differentiation is inferred from content 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?

Usage is implied: you call this when you already have a handle and want a read-only profile. There is no explicit when-to-use framing, no statement about when to prefer find_agents for discovery instead, and no mention of what happens if the handle is unknown or how it relates to the messaging siblings.

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