Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Forms question

forms_questions_get
Read-onlyIdempotent

Fetch a single form question's settings by survey and question ID to get its label, slug, type, and presentation flags.

Instructions

One question's settings by id — label, slug, type and common presentation flags.

Where questions_list returns every question grouped into pages, this fetches a single question keyed by question_id (take it from an item's id in questions_list). Type-specific detail (validators, options, conditions) comes in the fields of its type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
survey_idYesForm id (hex ObjectId) the question belongs to.
with_slugsNoRefer to other questions by slug instead of id.
question_idYesQuestion id (integer) to fetch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.122.1
    • addedInput schema / properties / with_slugs / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / with_slugs / default
      Previous value: -falseNew value: +null
    • removedInput schema / properties / with_slugs / type
      Removed value: -"boolean"
  2. First observedv0.67.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, so safety is covered. The description adds useful behavioral context about the return shape ('label, slug, type and common presentation flags') and notes that type-specific detail lives in type fields. It does not mention how with_slugs changes output rendering, but overall it extends beyond annotations.

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 sentences, front-loaded with what is returned and immediately followed by the list-vs-single contrast. Every sentence contributes: return content, usage contrast, and type-specific detail note. 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?

With no output schema, the description compensates by naming the returned fields and clarifying that type-specific detail comes from the question type. Combined with rich annotations and a fully described input schema, an agent has everything needed to call this get tool 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?

Schema coverage is 100%, so parameters are already documented. The description adds meaning by explaining that question_id should be taken from an item's 'id' in questions_list, linking the parameter to its source. It does not add anything for with_slugs, so it falls short of fully enriching all parameters.

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 specifies a clear verb (fetches) and resource (a single question), and explicitly names the list sibling it is not: 'Where questions_list returns every question grouped into pages, this fetches a single question.' An agent can distinguish it from forms_questions_list without opening any schema.

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 states the exact condition for using this tool: fetching one question keyed by question_id, and provides the source for that id ('take it from an item's id in questions_list'). It also contrasts directly with the list alternative, leaving no ambiguity about when to choose which.

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

Deploy Server

Other Tools