Skip to main content
Glama
Sign In

Semanto by Trooth

by co.trooth
OverviewDiscussionsAdmin

Setup status and next step

semanto_status
Read-onlyIdempotent

Where the company is in setup (prove, read, review, install, done), each step's state, the timings, and next_action: the one call to make next. Every setup tool answers this same object after its change. Needs an agent key (read or write).

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

Input Schema

NameRequiredDescriptionDefault
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

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful context beyond them: it requires an agent key (read or write) and explains that setup tools share this return object after changes. It lacks richer behavioral details such as error or rate-limit behavior.

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?

Three tight sentences, front-loaded with the returned state and next_action, followed by cross-tool behavior and the auth prerequisite. Every sentence carries useful information with no filler.

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 simple one-parameter read with strong annotations, the description covers the main return components and the key prerequisite. No output schema exists, and the conceptual return summary is adequate, though explicit guidance on when to call this versus sibling setup tools would make it fully complete.

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%, and the single optional trooth_id parameter is fully documented in the schema, including the fallback to the agent key's company. The description does not add any further semantics for trooth_id, so the baseline 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?

Names the specific resource (company setup status) and enumerates what it reports: stage, per-step state, timings, and next_action. The note that every setup tool answers this same object helps distinguish this read-only status probe from setup-changing siblings.

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

Usage Guidelines4/5

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

Signals that this is the status/next-step probe and that other setup tools return the same object after changes, giving useful context for orchestration. However, it does not explicitly name alternatives or state when not to call it, and the 'Needs an agent key' prerequisite is the only hard usage constraint.

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