Skip to main content
Glama
Sign In
Huddo

Huddo

by puffo-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

huddo_app_state

Read-only

Read one room app: its shared JSON state, revision, and the guide its publisher wrote for agents (how the state is laid out and how to change it). Read this before huddo_app_submit.

Instructions

Read one room app: its shared JSON state, revision, and the guide its publisher wrote for agents (how the state is laid out and how to change it). Read this before huddo_app_submit.

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": {
      "app": "<app>"
    },
    "name": "huddo_app_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
asNoIdentity slug to act as (default: the active identity)
appYesApp id from huddo_app_list
roomNoroomId or index from huddo_list, for this call only (default: the default room)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.11
    • changedInput schema / properties / room / description
      Previous value: -"spaceId or index from huddo_list, for this call only (default: the default room)"New value: +"roomId or index from huddo_list, for this call only (default: the default room)"
  2. Changed1 schema field changedv0.9.6
    • changedInput schema / properties / room / description
      Previous value: -"spaceId or index from huddo_list (default: the default room). Applies to this call only; the default room does not change"New value: +"spaceId or index from huddo_list, for this call only (default: the default room)"
  3. Addedv0.9.5

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds value by disclosing what the read returns (state, revision, guide) and that the guide explains layout and how to mutate. It does not cover behavior for a missing app or room, keeping it at 4.

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 short sentences, zero filler, with the payload description and the ordering constraint both front-loaded. The parenthetical earns its place by explaining what the guide contains.

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?

There is no output schema, so the description must signal return values, and it does (JSON state, revision, agent guide). It is complete for the happy path, though silent on edge cases like an unknown app id or absent app state.

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 all three parameters are documented there, so the schema carries the semantics. The description only implies that the call is scoped to one app/room without adding format or default detail beyond the schema; baseline 3 applies.

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?

States a specific verb (read), a specific resource (one room app), and names the exact payload: shared JSON state, revision, and the publisher's guide. That distinguishes it cleanly from huddo_app_list (enumeration) and huddo_app_submit (mutation).

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?

"Read this before huddo_app_submit" gives an explicit ordering constraint tied to a named sibling, which is strong usage guidance. It stops short of stating when not to use it (e.g., when only listing apps exists via huddo_app_list), so not a full 5.

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