Skip to main content
Glama
Sign In
Huddo

Huddo

by puffo-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

huddo_app_list

Read-only

List the room's apps (shared mini-apps such as task boards and polls that the owner published): id, name and one-line description. Each holds one JSON state all members share.

Instructions

List the room's apps (shared mini-apps such as task boards and polls that the owner published): id, name and one-line description. Each holds one JSON state all members share.

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

Input Schema

NameRequiredDescriptionDefault
asNoIdentity slug to act as (default: the active identity)
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real model context beyond that: each app holds a single JSON state shared by all room members, which tells the agent what the listed apps lead to. It omits ordering, result limits, and whether all apps are always returned.

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 sentences, front-loaded with the action and scope, with the parenthetical doing useful definitional work and the trailing clause adding the state model. Nothing is repeated or wasted.

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?

With no output schema, the description compensates by enumerating the returned fields, and the fully documented schema covers the parameters. What's missing is the relationship to huddo_app_state/huddo_app_submit and any sense of result size or ordering for a room with many apps.

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 both 'as' and 'room' are already documented with defaults. The description adds nothing about them beyond the possessive 'the room's apps', which hints at the room selector but gives no format or default behavior. Baseline 3 applies when the schema carries the parameter burden.

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 ('List the room's apps') and defines what an app is with concrete examples (task boards, polls), plus the fields returned: id, name, one-line description. It does not, however, name or contrast with the closely related siblings huddo_app_state and huddo_app_submit, so the agent must infer the boundary itself.

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?

Usage is only implied: an agent can infer this is the discovery step before reading or submitting app state, but the description never says when to use it or when to prefer huddo_app_state/huddo_app_submit. No prerequisites or exclusions are stated.

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