Skip to main content
Glama

mcphost

by dev.mcphost
OverviewDiscussionsAdmin

host.state.list

List keys (with their current values) in this tenant's key-value state namespace, optionally filtered by prefix.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax keys to return; default 100.
prefixNoOnly list keys starting with this prefix; default: all keys.
end_userNo"self" for the caller's own verified end-user identity, an explicit subject (only when this call carries no end-user identity of its own), or omit/null for the tenant-wide value.
tenant_keyNoThe key `signup` returned. Required only when this connection carries no Authorization: Bearer header -- when both are present, the header wins.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / end_user
      Added value: +{
+  "description": "\"self\" for the caller's own verified end-user identity, an explicit subject (only when this call carries no end-user identity of its own), or omit/null for the tenant-wide value.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Max keys to return; default 100."
    • addedInput schema / properties / prefix / description
      Added value: +"Only list keys starting with this prefix; default: all keys."
  3. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the operation lists keys with their current values within the tenant namespace and supports prefix filtering. However, it does not explicitly state that it is read-only, does not mention authentication requirements (beyond schema notes), or describe any potential side effects. The read-only nature is implied by 'list' but not explicitly disclosed.

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?

The description is a single, well-structured sentence that front-loads the primary action and includes the optional filter. It contains no redundant or filler text, earning full marks for conciseness.

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 list operation with fully documented parameters, the description covers the core behavior. It does not mention return format details beyond stating keys and values, which is sufficient. Given no output schema, the description is adequate for an agent to understand the operation's purpose and scope, though it could mention pagination or edge cases.

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%, with detailed descriptions for limit, prefix, end_user, and tenant_key. The tool description itself adds no parameter-specific information beyond what the schema already provides, so it meets the baseline for high coverage.

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?

The description clearly states the action (list), the resource (keys in the tenant's key-value state namespace), and an optional filter (by prefix). It is specific and unambiguous, distinguishing it from siblings like host.state.get (single key fetch) or host.state.query (search) without naming them.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention any exclusion conditions, prerequisites, or alternative tools. The parameter descriptions in the schema give some context (e.g., tenant_key required without bearer), but that is not usage guidance for tool selection.

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

All mcphost toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources