Skip to main content
Glama

insync_list_forms

Read-only

Lists patient intake and consent forms sent by the practice, defaulting to pending forms that still need completion and optionally including all submitted forms.

Instructions

List patient intake / consent forms the practice has sent. "pending" (the default) is what still needs completing; "all" includes submitted ones. Form names are shown; the form markup and the login credentials the portal embeds are never returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "insync_list_forms"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNocompact (default) projects each form to name, status and dates; "full" and "raw" return every OTHER field the portal sends for a form — never its embedded credentials or markup; "brief" returns one line per form: <name> — <ISO date> — <to complete | status>.
statusNo"pending" = awaiting the patient (Status "Sent"); "all" = every form. Default pending.pending

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • changedInput schema / properties / view / description
      Previous value: -"Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands; \"raw\" returns the upstream payload unprojected. compact projects each form to name, status and dates; \"full\" and \"raw\" return every OTHER field the portal sends for a form — never its embedded credentials or markup."New value: +"compact (default) projects each form to name, status and dates; \"full\" and \"raw\" return every OTHER field the portal sends for a form — never its embedded credentials or markup; \"brief\" returns one line per form: <name> — <ISO date> — <to complete | status>."
    • changedInput schema / properties / view / enum
      Previous value: -[
      -  "compact",
      -  "full",
      -  "raw"
      -]New value: +[
      +  "compact",
      +  "full",
      +  "raw",
      +  "brief"
      +]
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the read-only annotations, it discloses a meaningful behavioral constraint: form markup and embedded portal login credentials are never returned. That is exactly the kind of privacy/safety context annotations cannot express. It stops short of describing result volume or pagination behavior.

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 sentences, front-loaded with what the tool does and followed by the mode semantics and the safety note. No filler or redundancy.

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?

For a two-parameter, no-output-schema list tool, the definition covers purpose, mode selection, and what is withheld from results. A brief hint about what the default compact projection actually contains in the description would make it fully self-sufficient, but the schema covers that.

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 the baseline is 3, but the prose adds real meaning beyond the schema: it clarifies the intent of each status value (needs completing vs. includes submitted) rather than just restating the enum. The view modes, however, are left entirely to the schema.

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 opens with a specific verb and resource: 'List patient intake / consent forms the practice has sent.' That is enough to distinguish it from siblings like insync_list_documents or insync_list_surveys, though no sibling is named explicitly.

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?

It explains the status filter's purpose ('pending' is what still needs completing; 'all' includes submitted ones), which implies when to use each mode. It does not say when to reach for this tool instead of the documents or surveys listings, so selection guidance is only implied.

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