Skip to main content
Glama
Sign In

OrgLines

by com.orglines
OverviewDiscussionsAdmin

HR: Get form response

hr_get_form_response
Read-only

Read one filled-in form by its ASSIGNMENT id — the answers, who filled it, who it was about, and when. Read-only. Returns {response: null} when the assignment is not visible to the caller or has not been submitted yet. An EXIT-survey answer set is withheld (answers redacted) from a caller whose HR role may not read exit surveys — the same boundary the person's timeline applies.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "assignment_id": "<assignment_id>"
    },
    "name": "hr_get_form_response"
  }
}

Input Schema

NameRequiredDescriptionDefault
assignment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnly/non-destructive annotations by disclosing that authorization or non-submission is surfaced as {response: null} rather than an error, and that EXIT-survey answers are redacted for callers whose HR role forbids them. These are exactly the silent-failure and data-boundary behaviors an agent needs before trusting an empty result.

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?

Three tight sentences: purpose first, then the null-return caveat, then the redaction boundary. Capitalized emphasis on ASSIGNMENT and EXIT marks the two distinctions that matter; nothing is restated from the annotations or schema.

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 single-parameter, no-output-schema read tool, the definition covers the returned fields, the empty case, and the redaction case. An agent could call it correctly and interpret a null without further information.

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 schema is a bare untyped-semantics integer at 0% description coverage, so the description carries the load: it specifies that the id refers to an assignment (not a form, person, or application). It stops short of saying where to obtain such an id or confirming the integer format, which the schema supplies.

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 ('Read one filled-in form') plus the exact key ('by its ASSIGNMENT id') and enumerates what comes back: answers, filler, subject, timestamp. The emphasis on ASSIGNMENT id distinguishes it from form-definition lookups and from the list tools.

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?

Clear context for use: a single assignment by id, read-only, and the null-result condition when the assignment is invisible or unsubmitted. It does not name an alternative tool (e.g. the list-assignments path) for discovering ids or for bulk retrieval, so the agent must infer that routing.

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

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