Skip to main content
Glama

AI SENSE Free Public Tools

by com.aisenseapi
OverviewDiscussionsAdmin

Read human approval

read_human_approval
Read-onlyIdempotent

Check whether the person has answered a form from create_human_approval, and read the answer. For a group, partial means at least one person has answered and answered means all form links are complete. The group view contains counts, a tally and anonymous respondent numbers, never form tokens or notification settings. Set wait_seconds from 1 to 25 to wait for a change, or zero to read immediately. No API key, account or sign up is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
action_idYesThe UUID that create_human_approval returned.
wait_secondsNoWait up to this many seconds for a new answer. Zero returns immediately.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
tallyNo
statusYes
answeredNo
responseYes
action_idYes
responsesNo
respondentsNo
wait_reasonYes
waited_secondsYes
expire_datetimeYes
expire_timestampYes
created_at_datetimeYes
answered_at_datetimeYes
created_at_timestampYes
answered_at_timestampYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • addedInput schema / properties / wait_seconds
      Added value: +{
+  "default": 0,
+  "description": "Wait up to this many seconds for a new answer. Zero returns immediately.",
+  "maximum": 25,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedOutput schema / additionalProperties
      Added value: +false
    • addedOutput schema / properties / answered
      Added value: +{
+  "maximum": 20,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedOutput schema / properties / created_at_datetime
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / created_at_timestamp
      Added value: +{
+  "type": "integer"
+}
    • addedOutput schema / properties / ok
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / respondents
      Added value: +{
+  "maximum": 20,
+  "minimum": 2,
+  "type": "integer"
+}
    • addedOutput schema / properties / responses
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "answered_at_datetime": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "answered_at_timestamp": {
+        "type": "integer"
+      },
+      "respondent": {
+        "maximum": 20,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "response": {
+        "type": "object"
+      }
+    },
+    "required": [
+      "respondent",
+      "answered_at_timestamp",
+      "answered_at_datetime",
+      "response"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / properties / status / enum
      Previous value: -[
-  "pending",
-  "answered"
-]New value: +[
+  "pending",
+  "partial",
+  "answered"
+]
    • addedOutput schema / properties / tally
      Added value: +{
+  "type": "object"
+}
    • addedOutput schema / properties / wait_reason
      Added value: +{
+  "enum": [
+    "terminal",
+    "changed",
+    "timeout",
+    "immediate",
+    "unavailable",
+    "stalled"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / waited_seconds
      Added value: +{
+  "minimum": 0,
+  "type": "number"
+}
    • changedOutput schema / required
      Previous value: -[
-  "action_id",
-  "status",
-  "expire_timestamp",
-  "expire_datetime",
-  "answered_at_timestamp",
-  "answered_at_datetime",
-  "response"
-]New value: +[
+  "ok",
+  "action_id",
+  "status",
+  "created_at_timestamp",
+  "created_at_datetime",
+  "expire_timestamp",
+  "expire_datetime",
+  "answered_at_timestamp",
+  "answered_at_datetime",
+  "response",
+  "waited_seconds",
+  "wait_reason"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / action_id / description
      Added value: +"The UUID that create_human_approval returned."
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds meaningful behavioral detail: group semantics, what the group view contains and never contains, the effect of wait_seconds, and the lack of authentication requirements. No annotation contradiction exists.

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 purpose is front-loaded, and the remaining sentences each carry essential information: group behavior, group-view privacy constraints, wait behavior, and authentication requirements. There is no filler.

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?

For a simple read tool with a known output schema and safety annotations, the description covers everything an agent needs: what action to read, polling semantics, group interpretation, privacy boundaries, and auth requirements. Nothing essential 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 both parameters already have descriptive text. The description reinforces action_id as the UUID from create_human_approval and frames wait_seconds as waiting 'for a change,' but it does not add substantial parameter meaning beyond the schema.

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 opens with a specific verb and resource: 'Check whether the person has answered a form from create_human_approval, and read the answer.' It clearly ties the tool to its create-sibling and distinguishes it from the other read tools available.

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

Usage Guidelines4/5

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

It gives strong contextual guidance: it tells when to use it (after create_human_approval), explains partial vs. answered for groups, and prescribes wait_seconds behavior from 1 to 25 or 0 for immediate reads. It does not explicitly name alternatives or exclusions, but the usage context is clear.

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
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