Skip to main content
Glama
MCP 3DVista

MCP 3DVista

by juanchacon98

obtener_ayudante

Returns the TDVH helper source code for review or manual insertion into a 3DVista tour.

Instructions

Devuelve el codigo fuente del ayudante TDVH (para revisar o pegar manualmente).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does say the return value is source code, but it discloses nothing about permissions required, output size or format, whether the returned code matches what instalar_ayudante would write, or whether any side effects occur. For a zero-annotation tool this leaves meaningful gaps.

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?

A single short sentence with the action front-loaded and the purpose in parentheses. It is efficiently sized for a simple getter, with only minor ambiguity from the unexplained 'TDVH' acronym.

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?

With no output schema, the description must explain what comes back; it does so at a high level ('codigo fuente'), but not in terms of format, length, or whether the content is parameterized. For a zero-parameter retrieval tool this is minimally adequate rather than complete.

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 no parameters, so the baseline is 4. There is nothing parameter-related the description could add, and it correctly implies a parameterless retrieval.

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 states a specific verb and resource: it returns the source code of the 'ayudante TDVH'. The parenthetical 'para revisar o pegar manualmente' also implicitly separates it from the sibling instalar_ayudante, which would install rather than return code. The opaque acronym 'TDVH' keeps it from being fully self-explanatory.

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 gives an implied use case ('para revisar o pegar manualmente'), which suggests review or manual handling rather than automated installation. However, it never explicitly names instalar_ayudante as the alternative or states when not to use this tool, so the agent must infer the routing.

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