Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Forms fill suggestions

forms_filling_suggest
Read-onlyIdempotent

Autocomplete suggest-type form questions: pass a question slug and typed search text to get candidate answer values while filling a form.

Instructions

Autocomplete prompts for a suggest-type question while filling a form.

Pass the question slug (from filling_get) plus the search text; each returned item's id/text is a candidate value for the answer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoSearch text typed so far.
questionNoQuestion slug to suggest for.
parent_idNoParent object id scoping a Master/Detail lookup.
survey_idYesForm id or slug.
suggest_idNoComma-separated suggestion-object ids to resolve (the API's ``id``).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.122.1
    • removedInput schema / properties / survey
      Removed value: -{
-  "description": "Form id or slug.",
-  "type": "string"
-}
    • addedInput schema / properties / survey_id
      Added value: +{
+  "description": "Form id or slug.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "survey"
-]New value: +[
+  "survey_id"
+]
  2. First observedv0.67.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds genuine value beyond that: the return items' id/text are candidate values, which is important since no output schema exists. It omits pagination/rate-limit details, keeping it out of 5 territory.

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?

Two tight sentences, front-loaded with the core purpose followed by the concrete usage instruction. Every clause carries information; no filler.

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

Completeness4/5

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

With 5 parameters and no output schema, the description compensates by explaining both the input source (slug via filling_get) and the shape of returned candidates. Annotations cover the read-only/idempotent profile. Minor gaps remain around edge cases (e.g. null text or suggest_id resolution), but it is largely complete for invocation.

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 baseline is 3, but the description adds cross-parameter meaning: the 'question' slug originates from filling_get, and 'text' is the incremental search input driving the autocomplete. This ties the parameters to their source and purpose beyond the schema's terse field 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?

States a specific action and resource: 'Autocomplete prompts for a suggest-type question while filling a form.' It precisely scopes the tool to suggest-type questions and describes what is returned (candidate answer values). It does not explicitly contrast against the closest siblings (forms_filling_get / forms_filling_submit), though the 'while filling a form' framing implies its place in the workflow.

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 clear context — used while filling a form, only for suggest-type questions — and tells the agent where to obtain the required slug ('from filling_get'). It stops short of explicit when-not-to-use or naming an alternative tool, so it earns 4 rather than 5.

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