Skip to main content
Glama

NY LLC Publication (FileMyPublication)

Start an order

start_order
Read-onlyIdempotent

Returns the link to start an order with FileMyPublication for a service, prefilled with the county and the LLC's DOS ID when given. It never places an order: the person reviews the price and pays on the website.

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": "start_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
countyNoPublication only: the county in the LLC's Articles.
dos_idNoOptional: the LLC's NY Department of State ID number.
serviceNoWhich service. Defaults to publication.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds genuinely new behavior: the output is a handoff URL, values are prefilled when supplied, and no order is placed server-side. It does not say whether the returned link expires or is reusable, which is the main remaining behavioral gap.

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 short sentences with zero padding. The positive behavior (returns a prefill link) is front-loaded and the critical limitation follows immediately.

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 no output schema, the description correctly explains the return value as a link. All three parameters are covered and the human-payment model is disclosed. Minor gaps remain around link lifetime and what happens for non-publication services, but nothing an agent needs in order to call it is missing.

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 effect-level meaning: county and dos_id are prefill values used in the generated link, and county applies only to the publication service. The service default (publication) is left 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?

States a specific verb and artifact: 'Returns the link to start an order with FileMyPublication for a service', plus the prefill behavior. It is clearly distinct from cost/requirement lookups by being the ordering handoff, but it does not name or contrast any sibling tool explicitly.

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?

Gives a strong when-not: 'It never places an order: the person reviews the price and pays on the website', which tells the agent not to expect a completed transaction. It also scopes `county` to publication. It stops short of routing the agent to alternatives (e.g. cost or requirement lookups) before calling this.

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