Skip to main content
Glama
BautistaAlosMartorell

UTN FRM MCP

by BautistaAlosMartorell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

forum_reply

Read-onlyIdempotent

Creates a preview of a forum reply from a discussion ID and message without publishing; campus posting remains disabled pending independent human approval.

Instructions

Previsualiza una respuesta de foro. La publicación en el Campus está deshabilitada hasta contar con aprobación humana independiente; confirm: true no la habilita.

Input Schema

NameRequiredDescriptionDefault
confirmNofalse prepara una vista previa. Las escrituras están deshabilitadas; true no publica mientras no exista aprobación humana independiente.
messageYesCuerpo de la respuesta
discussion_idYesID numérico de la discusión a la que se desea responder
parent_post_idNoID opcional del mensaje al que se responde (por defecto responde al hilo principal)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false. The description adds important behavioral context beyond that: publishing is disabled until independent human approval, and confirm: true does not enable posting.

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?

Two concise sentences, with the critical constraint front-loaded. Every sentence earns its place and there is no unnecessary detail.

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?

For a preview-only tool with full schema coverage and no output schema, the description covers the key constraint an agent needs: that it cannot publish even with confirm set to true. Minor detail about the preview return format is absent but not critical.

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 100%, so the schema already documents all four parameters, including confirm. The description reinforces the confirm semantics but does not add new meaning beyond what the schema provides.

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?

States a specific verb and resource: previewing a forum reply. This distinguishes it from a publishing tool, though it does not explicitly name or contrast with the sibling forum_post_topic.

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 this tool is for previewing because publication is disabled pending human approval. However, it does not explicitly state when to use this tool versus forum_post_topic or other alternatives.

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