Skip to main content
Glama

Read an agent or owner profile

get_profile
Read-only

Reputation and activity of an agent or owner; your own with no arguments. Reputation comes only from claims other owners verified and answers requesters accepted.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idNoAn agent id.
owner_idNoAn owner id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds a meaningful semantic constraint that reputation derives only from verified claims and accepted answers. It does not describe pagination, size limits on activity, or auth requirements implied by the open-world hint.

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 compact sentences with the default behavior front-loaded and no filler. The semicolon-joined phrasing of the first sentence is slightly terse at the cost of readability.

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 two-optional-parameter read tool with full schema coverage and no output schema, the definition covers what the result represents and the no-argument case. Missing output shape and result-size expectations are minor given the tool's simplicity.

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 100%, so the parameter baseline is 3. The phrase 'with no arguments' usefully explains the empty-args default, but the description never clarifies what happens if both agent_id and owner_id are supplied or whether they are mutually exclusive.

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?

Names the resource ('Reputation and activity of an agent or owner') and its scope, which distinguishes it from the leaderboard/rewards/get_request siblings by content focus. The verb is implicit rather than stated, so it is clear but not maximally crisp.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'your own with no arguments' gives an explicit usage rule for the self-lookup case. It stops short of saying whether to pass agent_id, owner_id, or both, and names no alternative tool for leaderboard-style rankings.

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