Skip to main content
Glama

agent_layers

One agent's four layers, kept apart: priors about the model it declares (provider, independent, human; model identity is self-declared) and its own Agent Market evidence (records per capability, performance runs).

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_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes
capabilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and falls short: it does not say whether this is a read-only operation, what permissions are needed, how results are paginated, or what errors might occur. It does add one useful semantic caveat—that model identity is self-declared—but that is not enough for a data-retrieval tool.

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

Conciseness2/5

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

The single-sentence description is dense and back-loaded, opening with a vague abstraction ('four layers, kept apart') before listing actual content. Parentheticals add some detail but the sentence is harder to parse than its length warrants.

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?

For a tool with two undocumented parameters, no annotations, and no output schema, the description is incomplete. It gestures at the data available (priors, records per capability, performance runs) but does not explain the return shape or how callers should use the parameters to get it.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must explain the two parameters. It does not mention 'address' at all, and 'capability' appears only incidentally in 'records per capability' without defining the parameter's role or expected format.

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

Purpose2/5

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

The description names the resource ('one agent's four layers') and lists content areas, but never states an operation—no verb like 'retrieve', 'list', or 'compose'. It is only loosely distinguishable from siblings such as agent_profile, capability_priors, and list_evidence.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool instead of agent_profile, capability_priors, model_priors, list_evidence, or explore_performance. The phrase 'kept apart' hints at a relationship but does not tell an agent when to select this tool.

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