Skip to main content
Glama
travisbergen2

RPCS-1 Agent Tuner & Translation Bridge

Recommend AI agent configuration

recommend_agent_configuration
Read-onlyIdempotent

Diagnose why a deployed AI agent might fail and get tailored platform parameters, receiver profile values, and regime predictions from environment and task inputs.

Instructions

Diagnose why a deployed AI agent may fail. Takes environmental entropy, predictability, stakes, context horizon, and commitment style, then returns receiver profile values (TI, SG, FT, UE, AR), platform parameters (temperature, top_p, strategy), regime prediction, reasoning, and warnings. Optionally pass target_model to attach MEASURED per-model receiver posture (E-LIT table). Deterministic, stateless, read-only — does not store past recommendations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskNo
environmentNo
target_modelNoOptional: the actual model id this agent will run on (e.g. "claude-sonnet-4-6"). When it matches a measured per-model receiver entry (E-LIT table), measured translation directives and evidence-graded posture data are attached to platform_parameters.
target_platformNoThe platform whose runtime parameters should be recommended.anthropic

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
warningsYes
reasoningYes
confidenceYes
predicted_regimeYes
receiver_profileYes
platform_parametersYes
imm_principles_appliedYes
Behavior4/5

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

Annotations already indicate readOnlyHint, idempotentHint, destructiveHint. Description adds 'Deterministic, stateless, read-only — does not store past recommendations,' which reinforces and extends the annotation context. No contradictions.

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?

The description is three sentences, front-loaded with purpose, then input/output summary, then behavioral traits. Every sentence adds value with no wasted words.

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

Completeness5/5

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

Given the tool's complexity (4 parameters with nested objects, output schema exists), the description covers purpose, inputs, outputs, and behavioral traits adequately. Annotations and return types are well specified.

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 50% and most fields have individual descriptions. The tool description lists input categories but does not add new meaning beyond the schema. Baseline score of 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 tool diagnoses why a deployed AI agent may fail and returns configuration recommendations, specifying input factors and output structure. It distinguishes itself from sibling tools (interpret, normalize, rewrite) which are text-oriented.

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 diagnosing agent failure but lacks explicit guidance on when to use vs alternatives or when not to use. No comparison with siblings or exclusions are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/travisbergen2/rpcs1-sdk'

If you have feedback or need assistance with the MCP directory API, please join our Discord server