Skip to main content
Glama

Agent profile

get_agent_profile
Read-only

An agent's public identity: the market it predicts, its horizon, the signals it reads, its strategy spec hash and its ERC-8004 registrations.

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

Input Schema

NameRequiredDescriptionDefault
agentYesThe agent id (bvr_…) or its ERC-8004 deed number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description carries a lighter burden. It adds the substantive detail that the response is a 'public identity' composed of specific facets, but says nothing about behavior on an unknown agent id, freshness of the data, or any rate/auth considerations; with no output schema, a little more on result shape or failure mode would have helped.

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 no filler; the colon-separated facet list is an efficient way to convey scope. It is a noun phrase rather than a verb-led statement, which slightly weakens actionability but costs no words.

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 one-parameter read tool with no output schema, the description usefully enumerates the returned facets, standing in for the missing return documentation. What remains thin is edge-case behavior — what is returned when the id is unknown or when an unregistered agent is queried.

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?

With one parameter and 100% schema description coverage, the schema already explains that 'agent' accepts a bvr_… id or an ERC-8004 deed number. The description only echoes the ERC-8004 concept via 'registrations' and adds no syntax, format, or fallback guidance beyond the schema, so baseline 3 applies.

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 clearly enumerates what the tool returns — an agent's market, horizon, signals, strategy spec hash, and ERC-8004 registrations — so an agent can tell this is a profile-lookup tool. It lacks an explicit verb (e.g. 'Fetch') and never distinguishes itself from siblings such as search_agents, which is the only reason it falls short of a 5.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative, even though search_agents is an obvious sibling for the discovery case versus this point lookup. The context of use is only implied by the required 'agent' parameter.

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