Skip to main content
Glama

Get Lead Form

get_lead_form
Read-only

Get lead form details for a community managed by the authenticated Nas.com user. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "communityId": "<communityId>",
      "formId": "<formId>"
    },
    "name": "get_lead_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
formIdYesLead form ID, from a Nas.com lead form listing.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / formId / description
      Added value: +"Lead form ID, from a Nas.com lead form listing."
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare a safe read (readOnly=true, destructive=false, openWorld=false), so the bar is lower, and the description still adds substantial context: hard denial for FREE businesses regardless of feature rows, a mandatory access-check call, and required surfacing of grace-period warnings and resubscribe links. It stops short of describing what the returned details contain or how access failures manifest.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose then pivots entirely to access control, with overlapping restatements ('check business permissions', 'Call check_business_tool_access before collecting inputs', 'never proceed when access is blocked') that repeat the same gate three ways. The repeated emphasis consumes space that could have described the payload.

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

Completeness3/5

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

The tool is simple (two required params, read-only, no nesting), but has no output schema, so the description is the only place a caller could learn what 'details' are returned — and it says nothing about that. Prerequisite coverage is thorough; result coverage is absent.

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 100%, so both formId and communityId are already documented, including the 'never invent an ID' caution and the list_businesses provenance hint. The description adds only the scoping constraint that the community must be one the authenticated user manages.

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 verb and resource ('Get lead form details') and scopes it to a community managed by the authenticated Nas.com user. It does not distinguish itself from adjacent readers such as get_lead_form_analytics, get_lead_form_submission, or list_lead_form_applicants, so an agent must infer that this returns form definition/metadata rather than responses or applicants.

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?

Gives strong precondition guidance: check business permissions, FREE businesses are blocked, call check_business_tool_access before collecting inputs, surface grace-period warnings. However, this is entitlement gating rather than tool-selection guidance; nothing says when to pick this over sibling lead-form readers.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources