Skip to main content
Glama

AI SENSE Free Public Tools

by com.aisenseapi

Read human approval

read_human_approval
Read-onlyIdempotent

Check whether the person has answered a form from create_human_approval, and read what they chose. The status field is pending or answered. Note carefully that answered does NOT mean approved: it means a reply arrived, and which option they picked is inside the response field, so read it before acting. Pending simply means nobody has answered yet - poll again after a pause. This is an immediate check, not a blocking wait, and the request expires 24 hours after it was created. No API key, no account and no sign up: call it directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
action_idYesThe UUID that create_human_approval returned.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYes
responseYes
action_idYes
expire_datetimeYes
expire_timestampYes
answered_at_datetimeYes
answered_at_timestampYes

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent), the description adds crucial behavioral details: it is immediate and non-blocking, expires after 24 hours, and clarifies that 'answered' does not mean 'approved'—just that a reply arrived. It also notes no API key is needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat verbose but well-structured: first states purpose, then explains status meanings, then behavior. It covers necessary nuances without excessive redundancy, though it could be slightly more compact.

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?

Given that an output schema exists (so return values need no explanation), the description is complete: it covers purpose, usage (polling), behavior (non-blocking, expiration), status semantics, and authentication requirements. It leaves no critical gaps for the agent to function correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The parameter action_id is fully described in the schema as 'The UUID that create_human_approval returned.' The description reinforces this by referencing create_human_approval, adding a small amount of context beyond the schema, so a 4 is appropriate.

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 that the tool checks whether a person has answered a form from create_human_approval and reads the status. It distinguishes itself from siblings like read_webhook_capture and read_temporary_data by focusing on human approval status.

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?

It provides explicit when-to-use guidance: call after creating a human approval to poll for an answer, and suggests polling again after a pause. It also clarifies it's non-blocking and expires after 24 hours, which informs the polling strategy.

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

All AI SENSE Free Public Tools toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

Each tool is centered on a distinct resource or action, and the read_* tools clearly map to their create_* counterparts. The main source of ambiguity is create_agent_wake, which overlaps conceptually with create_human_approval and create_webhook_capture because it also involves webhooks and human form replies.

Naming Consistency5/5

Tool names consistently follow a verb_noun pattern in snake_case, with clear create_*/read_* pairs and standalone helpers like generate_uuid and get_current_time. No mixed casing or arbitrary verb styles appear.

Tool Count5/5

Ten tools is a well-scoped size for a general-purpose public utility server. Each tool covers a distinct need, and the collection feels intentionally curated rather than bloated or sparse.

Completeness4/5

The create/read pairs provide reasonable coverage for approvals, webhook capture, and temporary storage, plus useful standalone utilities. The noticeable gaps are missing cancellation, deletion, or status operations for agent wakes and temporary resources, but these do not severely cripple typical workflows.

Resources