Skip to main content
Glama

Teamtailor Ops Control Plane

by app.vercel.ats-ops-control-plane-gateway

get_form

Get one form. Forms and application structure metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesform ID.
includeNo
query_jsonNoAdditional documented query parameters, including bracketed filter keys.
path_paramsNoValues for path placeholders such as {id} in a write operation.
detail_profileNooperational (default) returns a compact recruiting-ops projection with names, prose, and other personal fields omitted; pass full to include the raw API payload with those fields.operational

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changed
    • changedInput schema / properties / detail_profile / default
      Previous value: -"full"New value: +"operational"
    • changedInput schema / properties / detail_profile / description
      Previous value: -"full returns raw API payload; operational returns a compact recruiting-ops projection."New value: +"operational (default) returns a compact recruiting-ops projection with names, prose, and other personal fields omitted; pass full to include the raw API payload with those fields."
    • addedInput schema / properties / path_params
      Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "Values for path placeholders such as {id} in a write operation.",
+  "type": "object"
+}
    • removedInput schema / properties / reason
      Removed value: -{
-  "description": "Required when detail_profile=full.",
-  "maxLength": 500,
-  "minLength": 12,
-  "type": "string"
-}
  2. First observed

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states what the tool gets, not whether it is read-only, what data is returned, or any side effects. The phrase 'application structure metadata' is vague and adds limited transparency.

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 extremely concise, with no filler. 'Get one form' is front-loaded and effective, and the clarifying clause is short. However, the phrase 'Forms and application structure metadata' is slightly vague, preventing a perfect score.

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?

The tool has 5 parameters, nested objects, and no output schema or annotations, yet the description is minimal. It does not explain return values, filtering behavior, or how parameters like include and query_json interact. The description is inadequate for the tool's complexity.

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 80%, so the schema already documents most parameters. The description adds no detail about id, include, query_json, path_params, or detail_profile beyond what the schema provides. Baseline score of 3 is appropriate since the schema does most of the work.

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 'Get one form' uses a specific verb and resource, clearly indicating it fetches a single form. It distinguishes itself from sibling list_forms by emphasizing 'one', and the added phrase 'Forms and application structure metadata' helps contextualize the resource.

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

Usage Guidelines3/5

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

The description implies usage context ('Get one form') but does not explicitly state when to use this tool versus list_forms or other get_* tools. No alternatives or exclusion criteria are mentioned.

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

All Teamtailor Ops Control Plane 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

C2.8/5.0
Disambiguation4/5

Most tools have clearly distinct purposes due to specific resource names and detailed descriptions. However, the large number of similar get/list pairs (e.g., get_activity, get_answer) could cause an agent to misselect without careful reading, slightly reducing clarity.

Naming Consistency5/5

The naming follows a strict and predictable verb_noun pattern (list_/get_/create_/update_) using snake_case throughout. The only outlier is 'api_request', but it is a generic tool and does not break the overall pattern.

Tool Count3/5

With 62 tools, the set is large but arguably justified by the breadth of the Teamtailor domain (candidates, jobs, applications, interviews, notes, etc.). Still, it exceeds the typical 3-15 range for high coherence, making navigation heavy for agents.

Completeness3/5

The tool set provides comprehensive read access (get/list) for most entities, but lacks delete operations entirely and has limited update coverage (only candidate, job, job_application). The 'api_request' tool can compensate, but the surface has notable gaps in mutation capabilities.

Resources