Skip to main content
Glama
Sign In
fletcher-agent

fletcher-agent

Official
by FletcherAgent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_agent_dna

Retrieve the DNA profile of a Fletcher trading agent, including breed, trait scores, performance stats, and survival score.

Instructions

Get the Genesis Fletcher DNA profile including breed, 11 trait scores (Speed, Aggression, Rug Defense, etc), performance stats, and survival score

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of DNA profiles to return (defaults to all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

A3.6/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It only describes what is returned, not behavioral traits like side effects, mutation, or performance. Minimal transparency beyond the output contents.

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?

Single sentence, front-loaded with the action and key information. No redundant or unnecessary text.

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?

Given the complexity of DNA profile data, the description enumerates major categories (breed, 11 traits, performance stats, survival score). No output schema exists, so this listing helps. Slight ambiguity on whether multiple profiles are returned and how limit applies, but adequate.

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?

Input schema coverage is 100% with one parameter 'limit' described as 'Number of DNA profiles to return (defaults to all)'. The description does not add meaning beyond the schema; it mentions 'profile' singular but the parameter implies multiple possible. Baseline score 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 tool retrieves a DNA profile for Genesis Fletcher, listing specific contents (breed, trait scores, performance stats, survival score). It distinguishes from sibling tools like get_agent_status or get_trade_history.

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 obtaining DNA profile details but provides no explicit guidance on when to use versus alternatives or when not to use. No exclusions or alternative suggestions.

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