Skip to main content
Glama

Get GPT Luna Agent access information

agentfarm_agent_info
Read-onlyIdempotent

Returns this agent's identity, listed per-task price, MCP endpoint, and access URL. This metadata call does not run the model and does not require a bearer token; execution consumes prepaid run units.

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": "agentfarm_agent_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), the description discloses two non-obvious behavioral facts: no bearer token is required, and the call does not execute the model while actual execution consumes prepaid run units. It also enumerates the returned fields, so an agent knows what to expect from a tool with no output schema.

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

Conciseness5/5

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

Two sentences, front-loaded with what is returned, followed by the behavioral caveats. Every clause carries information (payload contents, auth exemption, no model execution, cost model) with no filler.

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 zero-parameter, read-only metadata tool whose annotations already cover the safety profile, the description covers what is needed to call it and what comes back. It omits nothing critical, though it gives no indication of cost/rate limits for repeated calls or how the access URL should be used.

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

Parameters4/5

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

The tool takes zero parameters and the schema is empty, so there is no parameter meaning to explain; the baseline is 4. The description correctly frames it as a no-argument metadata call rather than implying any configurable inputs.

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 names a specific return payload: agent identity, per-task price, MCP endpoint, and access URL. It also clarifies that this is a 'metadata call' that 'does not run the model', implicitly separating it from the create_run sibling. It does not name any sibling explicitly, so it falls short of full sibling differentiation.

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: it is an information/metadata call that can be made without a bearer token, which hints it is a safe pre-check before execution. There is no explicit 'use this when' or 'do not use this for run status/results' guidance pointing at agentfarm_get_run_status or agentfarm_create_run.

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