Skip to main content
Glama
Sign In
valta-mcp

valta-mcp

by Valta-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

valta_get_agent

Retrieve details for an AI agent, including its status and financial balance, to monitor governance and audit trails.

Instructions

Get details for a single agent, including status and balance.

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": {
      "agentId": "<agentId>"
    },
    "name": "valta_get_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYesThe agent ID to look up

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It only states what the tool returns, not that it is a read-only operation (implied but not explicit). It does not disclose side effects, authentication requirements, or rate limits, which are important for mutation-less tools.

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?

The description is concise (10 words) and front-loaded with the action. However, it omits some useful context that could be added in a few more words without sacrificing conciseness, such as clarifying it is a read-only lookup.

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

Completeness3/5

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

For a simple single-parameter tool with no output schema, the description gives a reasonable summary ('including status and balance') but does not fully describe the return structure, error cases, or mention that it is a read operation. It is adequate but not thorough.

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% (the only parameter 'agentId' has a description). The tool's description adds minimal value beyond the schema, only mentioning 'including status and balance' which relates to output, not parameters. Baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states the action ('Get details') and resource ('single agent'), and specifies included content ('status and balance'). It implicitly differentiates from sibling 'valta_list_agents' by targeting a single agent rather than a list.

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?

The description implies usage for retrieving a single agent's details but provides no explicit guidance on when to use this tool versus alternatives like 'valta_get_agent_run' or 'valta_check_balance'. No prerequisites or exclusions are mentioned.

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

Deploy Server

Other Tools