Skip to main content
Glama

mcphost

by dev.mcphost
OverviewDiscussionsAdmin

host.state.delete_rows

Delete rows from a declared table matching an optional where filter (same grammar as host.state.query); omitting where deletes every row in the table.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableYesName of the declared table to delete rows from.
whereNoOptional filter, same grammar as host.state.query; omit to delete every row.
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 / table / description
      Added value: +"Name of the declared table to delete rows from."
    • addedInput schema / properties / where / description
      Added value: +"Optional filter, same grammar as host.state.query; omit to delete every row."
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and explicitly warns that omitting where deletes every row in the table, which is critical destructive behavior. It does not mention irreversibility or permissions, but the core risk is well 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?

A single sentence conveys the action, scope, filter behavior, and the critical consequence of omitting the filter. There is no wasted text, and the most important warning is front-loaded.

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 destructive row-deletion operation, the description covers the essential behavior and the optional filter semantics. With no output schema needed and full parameter schema coverage, the remaining gaps such as permissions or return values are minor.

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 the schema already documents all four parameters. The description adds a useful reference to host.state.query's grammar and repeats the all-rows deletion warning, but it does not provide substantial extra meaning beyond the schema.

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?

The description clearly identifies the operation as deleting rows from a declared table and specifies the optional where filter. It is distinct from host.state.delete and other sibling tools, though it does not explicitly name a sibling for differentiation.

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?

The intended use is implied: delete rows from a declared table, optionally filtered. It mentions that host.state.query provides the filter grammar, but it does not explicitly say when to prefer this tool over host.state.delete or other alternatives.

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