Skip to main content
Glama

100Hires - AI ATS & Recruitment Software

by com.100hires
OverviewDiscussionsAdmin

hires_list_forms

Read-only

List application forms of a company.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sizeNo
viewNosummary omits the questions arraysummary
company_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / company_id / description
      Removed value: -"Target company ID."
    • removedInput schema / properties / page / description
      Removed value: -"Page number."
    • removedInput schema / properties / size / description
      Removed value: -"Page size."
    • changedInput schema / properties / view / description
      Previous value: -"Response shape. Default `summary` omits the embedded `questions` array. Use `full` only when the full question list is needed; call hires_get_form for a single form."New value: +"summary omits the questions array"
  2. Changed1 schema field changed
    • addedInput schema / properties / view
      Added value: +{
+  "default": "summary",
+  "description": "Response shape. Default `summary` omits the embedded `questions` array. Use `full` only when the full question list is needed; call hires_get_form for a single form.",
+  "enum": [
+    "summary",
+    "full"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, and the description adds no behavioral details beyond that. It does not disclose pagination behavior, defaults for page/size, whether company_id is required despite being listed as optional, or what fields are returned.

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 a single clear sentence with no filler or redundant wording. It is front-loaded and easily parsed, though it could earn a higher score by adding more useful context without becoming verbose.

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

Completeness2/5

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

With four parameters, only 25% schema coverage, and no output schema, the description leaves significant gaps. An agent cannot tell whether company_id is effectively required, what pagination defaults apply, or what the response structure looks like, making the description minimally viable but incomplete for confident invocation.

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

Parameters2/5

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

Schema description coverage is only 25%, with only the view parameter documented. The description's phrase 'of a company' hints at company_id, but it does not explain page, size, or the implications of choosing summary versus full view, so it fails to compensate for the schema's sparse parameter descriptions.

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 states a specific action and resource: listing application forms for a company. It is clear enough to distinguish from sibling tools like hires_get_form (single form retrieval) and hires_list_questions (listing questions), though it does not explicitly mention those differentiators.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives such as hires_get_form or hires_list_applications. There is no mention of prerequisites, such as needing a company_id, or scenarios where this list is preferable.

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

All 100Hires - AI ATS & Recruitment Software toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources