Skip to main content
Glama

moltbound_requirements

Fields to ask the human for a service. SANDBOX: use fictitious data only. Do not enter real personal details. Pass service_id to inspect any of the 20 services.

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": {
      "session_token": "<session_token>"
    },
    "name": "moltbound_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
service_idNoOptional service_id override (e.g. home_building, electricity)
session_tokenYesFrom moltbound_start_session, moltbound_human_sim_headless or moltbound_human_sim_verify

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / session_token / description
      Previous value: -"From moltbound_start_session or moltbound_human_sim_verify"New value: +"From moltbound_start_session, moltbound_human_sim_headless or moltbound_human_sim_verify"
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuinely important trait: this is a sandbox where only fictitious data should be entered. It says nothing about whether requirements differ per service, what happens with an invalid service_id, or how the session token gates access, so behavioral disclosure is partial.

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?

At three short sentences there is no padding, and the sandbox warning is prominently placed. The opening sentence is grammatically awkward and does not front-load a clear action, which keeps it below a 5.

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?

For a two-parameter read tool with no output schema and no annotations, the description covers the safety context but not what the returned fields look like or how they should be consumed. An agent can call it, but must explore the output blind.

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%, so the schema already documents both parameters, and the baseline is 3. The description adds only marginal meaning beyond the schema: it clarifies that service_id selects among 20 available services rather than acting as a simple override.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "Fields to ask the human for a service" signals that the tool surfaces the data requirements for a service, but it lacks an explicit verb (get/list/describe) and never names how it differs from siblings like moltbound_list_services or moltbound_get_quotes. The service_id sentence hints that it can be scoped to one of 20 services, but the core operation remains ambiguous.

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?

The only usage cue is "Pass service_id to inspect any of the 20 services," which covers one parameter but not when to call this tool versus list_services or get_quotes. There are no exclusions, prerequisites, or workflow context (e.g., call before requesting a quote).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources