Skip to main content
Glama
Sign In
GAIIA Expert Proxy (MCP Server)

GAIIA Expert Proxy (MCP Server)

by dapooleygmailcom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gaiia_set_active_expert

Select an expert by email to apply their expertise to code transformations.

Instructions

Select an expert to use for code transformations.

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": {
      "email": "<email>"
    },
    "name": "gaiia_set_active_expert"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe email of the expert

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It does not disclose side effects (e.g., overwriting previous selection), validation of email, or whether the expert must exist. The behavior is under-specified.

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?

One short, front-loaded sentence that clearly states the tool's action. It is concise and contains no fluff, though it could benefit from additional context.

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?

Given low complexity (1 param, no output schema), description is somewhat complete but fails to mention return value or prerequisites (e.g., expert must exist). Lacks detail for fully uninformed use.

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% with one string parameter 'email' described as 'The email of the expert'. Description does not add extra meaning beyond the schema, so baseline 3 applies.

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?

Description uses specific verb 'select' and resource 'expert', and distinguishes from sibling tools like gaiia_list_experts and gaiia_transform by implying selection of an active expert for transformations.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., before gaiia_transform or after listing experts). No explicit when-not or exclusion criteria.

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