Skip to main content
Glama
avarole-mcp
by Sbaig3229

avarole_get_agent

Read-only

Retrieve a support agent's name, voice, system-prompt instructions, and plain settings by agent ID; credentials are excluded.

Instructions

One agent's settings: name, voice, instructions (system prompt) and its plain settings. Credentials are never shown.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "avarole_get_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine beyond-annotation context: what fields are exposed and the redaction guarantee 'Credentials are never shown', which tells the agent not to expect secrets. It omits behavior on an invalid/missing agent_id, which keeps it from a 5.

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?

Two short sentences, return contents front-loaded and the security caveat trailing, with no filler. The phrase 'its plain settings' is vague and slightly redundant with the enumerated fields, which is the only waste.

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 simple read-only single-entity fetch with annotations covering the safety profile and no output schema, the description does most of the work by naming the returned fields and the credential redaction. Missing detail on not-found behavior and on whether instructions can be large/truncated is a minor gap.

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 0%, so the description carries the burden for agent_id and it provides no format guidance or hint about where to source the identifier (e.g., from avarole_list_agents). The parameter name is self-evident and 'one agent' frames its meaning, so a baseline 3 is fair rather than lower.

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-resource pair implicitly (retrieve 'One agent's settings') and enumerates the returned fields: name, voice, instructions/system prompt, plus 'plain settings'. The singular 'one agent' implicitly contrasts with avarole_list_agents, though the sibling is never named.

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: the singular scope plus the required agent_id make it evident this is a single-agent lookup rather than a listing. There is no explicit 'use this when...' statement and no named alternative such as avarole_list_agents for enumerating agents.

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