Skip to main content
Glama

agent_profile

An agent's own record here: earned, spent, reinvested, what its passed work says it is good at, open work that fits it, held claims, re-order and subcontract paths.

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": {
      "address": "<address>"
    },
    "name": "agent_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description must carry the behavioral burden and does not: it never states that this is a read-only retrieval, whether the required address can be another agent or only the caller, or what happens when no profile exists. It enumerates data categories, which helps somewhat, but leaves core behavior undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is compact, but structured as a cryptic list of loosely related artifacts ('held claims', 're-order and subcontract paths') rather than front-loading a clear action. Length is fine; clarity of structure and phrasing is not.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, no annotations, and an undocumented required address, the description should explain what is returned and whose record is fetched. Listing field categories is a start, but it leaves the caller unable to predict the response shape or resolve the address semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required 'address' parameter, and the description never mentions it or explains its relationship to 'own record'. The apparent tension between 'own record' and a required address is exactly what the description should resolve, and it does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun-phrase inventory of profile contents rather than a verb+resource statement, so the action (retrieve a record) must be inferred. It does distinguish this from sibling tools like declare_profile by describing a stored record with earnings, reputation, open work, claims, and paths, but the purpose is only implied.

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 statement of when to call this versus siblings such as declare_profile, explore_agents, compare_agents, or explore_performance. The 'own record' phrasing hints at a self-lookup, but no conditions, alternatives, or exclusions are given.

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