Skip to main content
Glama

get_form

Retrieve details of a specific Tally form by its ID to access form information for management or integration purposes.

Instructions

Retrieve details of a specific Tally form

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formIdYesID of the form to retrieve

Implementation Reference

  • Registration of the 'get_form' tool including its input schema in the _handleToolsList method. This defines the tool's name, description, and expected input (formId).
      name: 'get_form',
      description: 'Retrieve information about a specific Tally form',
      inputSchema: {
        type: 'object',
        properties: {
          formId: { type: 'string', description: 'ID of the form to retrieve' }
        },
        required: ['formId']
      }
    },
  • Input schema definition for the 'get_form' tool requiring a formId string.
        type: 'object',
        properties: {
          formId: { type: 'string', description: 'ID of the form to retrieve' }
        },
        required: ['formId']
      }
    },
  • Core implementation of form retrieval via Tally API in TallyApiClient.getForm, which makes the HTTP GET request to /forms/{formId} and validates the response using TallyFormSchema. This is the underlying service method used by tools.
    public async getForm(formId: string): Promise<TallyForm> {
      if (this.isMockEnabled()) {
        const mockRes = await tallyApiMock.getForm(formId);
        return mockRes.data;
      }
      const url = `/forms/${formId}`;
      const response = await this.get(url);
      return validateTallyResponse(TallyFormSchema, response.data);
    }
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. While 'retrieve' implies a read operation, it doesn't specify whether this requires authentication, has rate limits, returns structured data, or handles errors. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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?

For a retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'details' are returned (e.g., form structure, metadata, or both), nor does it cover error cases or authentication requirements. Given the lack of structured data elsewhere, the description should provide more complete context.

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?

The input schema has 100% description coverage, with the single parameter 'formId' clearly documented. The description doesn't add any additional parameter context beyond what the schema provides, such as format examples or sourcing guidance. With complete schema coverage, the baseline score of 3 is appropriate.

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 clearly states the action ('Retrieve details') and resource ('specific Tally form'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'list_forms' or 'get_submissions', which would require more specific scope information to earn a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list_forms' (for multiple forms) or 'get_submissions' (for form responses). It also doesn't mention prerequisites or contextual constraints, leaving the agent to infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/learnwithcc/tally-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server