Skip to main content
Glama
Sign In

Semanto by Trooth

by co.trooth
OverviewDiscussionsAdmin

Choose Basic or the full signed copy

semanto_setup_choose
Idempotent

Completes the receipt step. basic keeps the company on Semanto Basic; full moves it to the signed copy of the whole site. Needs an agent key with write scope (owner scope where only the owner may).

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": {
      "path": "<path>"
    },
    "name": "semanto_setup_choose"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesbasic or full.
trooth_idNoThe company's Trooth ID, for example acme. Leave it out to use the company the agent key belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly=false, idempotent=true, destructive=false), and the description adds a genuinely useful auth requirement: an agent key with write scope, plus owner scope where applicable. It does not say whether the full choice is reversible or what state the site ends up in, but the privilege disclosure is real added value.

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?

Three tight sentences with no filler, and the option semantics are front-loaded after a short lead. Only the opaque 'Completes the receipt step' opener costs it a point, since it delays the actionable content.

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?

For a two-parameter, idempotent, non-destructive mutation with full schema coverage and no output schema, the description supplies the decision semantics and the permission requirement an agent needs. No expected return format is needed because there is no output schema.

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?

Schema coverage is 100%, so baseline is 3, but the description exceeds it: the schema only says 'basic or full.' while the description explains the actual consequence of each enum value. The optional trooth_id is left to the schema, which documents it adequately, including the default-to-agent's-company behavior.

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 names a specific decision (basic vs full) and spells out the outcome of each: 'basic keeps the company on Semanto Basic; full moves it to the signed copy of the whole site.' The framing 'Completes the receipt step' is jargon that requires prior setup context to decode, and the tool is not explicitly differentiated from nearby setup siblings like semanto_setup_confirm or semanto_setup_save_for_later.

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?

It effectively describes when each parameter value applies (stay on Basic vs move to the signed copy), which is the core usage decision. However, it never states when this tool should be invoked relative to the other setup tools (confirm, save_for_later, resume) or any preconditions, so usage is only implied.

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

All Semanto by Trooth toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources