Skip to main content
Glama
Sign In

Elicitly Pro

by ai.elicitly
OverviewDiscussionsAdmin

Check an elicitation's status

elicit_status
Read-only

Non-blocking status check for an elicitation you created: returns { status } — pending | submitted | declined | canceled | expired | consumed. Read-only and repeatable (never consumes the result); use elicit_await to block on a decision and elicit_result to fetch the outcome.

Input Schema

NameRequiredDescriptionDefault
elicitationIdYesThe `elicitationId` returned by the creating tool (elicit_approval, elicit_selection, or elicit_proposal).

Output Schema

NameRequiredDescriptionDefault
statusYesThe request's current lifecycle state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +{}
  2. Changed2 schema fields changed
    • addedInput schema / properties / elicitationId / description
      Added value: +"The `elicitationId` returned by the creating tool (elicit_approval, elicit_selection, or elicit_proposal)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "status": {
+      "description": "The request's current lifecycle state.",
+      "enum": [
+        "pending",
+        "submitted",
+        "declined",
+        "canceled",
+        "expired",
+        "consumed"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the genuinely important behavioral traits beyond that — non-blocking, repeatable, and 'never consumes the result' (contrasting with elicit_result, which does). It also enumerates the possible status values the caller will observe.

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 dense sentence that front-loads the core behavior, then the return shape, then the alternative tools. No filler, no repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Read-only safety is covered by annotations, the return value is enumerated inline (and an output schema exists), and the sibling routing is spelled out. Nothing an agent needs to invoke this correctly is missing.

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% and the single parameter's origin is already documented in the schema ('returned by the creating tool'). The description's phrasing 'an elicitation you created' adds a mild ownership constraint but nothing about id format or lookup behavior. Baseline 3 applies when the schema carries the parameter detail.

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 and resource ('non-blocking status check for an elicitation') and immediately differentiates itself from two named siblings, elicit_await and elicit_result. An agent can pick this tool without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing: use this for non-blocking checks, elicit_await to block on a decision, elicit_result to fetch the outcome. It also implicitly scopes usage to elicitations the caller created.

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

All Elicitly Pro toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources