Skip to main content
Glama

NY LLC Publication (FileMyPublication)

Search FileMyPublication's guides

search_guides
Read-onlyIdempotent

Finds FileMyPublication's plain-English guides on New York LLC publication by topic, e.g. 'missed deadline', 'affidavit', 'Brooklyn cost', 'foreign LLC', 'single member home address'. Returns titles, summaries and links.

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": {
      "query": "<query>"
    },
    "name": "search_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat the person wants to know.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile needs no restating. The description adds genuinely new behavioral information: the content domain is plain-English guides and the response consists of titles, summaries and links. It omits any mention of result limits or ranking, which keeps it from a 5.

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 the action and domain, with the example list doing real work by demonstrating query style. Nothing is redundant or padded.

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 single-parameter, read-only retrieval tool with full schema coverage and no output schema, the description supplies the missing return shape (titles, summaries, links) and the content domain. Mild incompleteness around result count or behavior on zero matches keeps it below a 5.

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% and the schema already labels the param as 'What the person wants to know'. The description goes beyond that by showing the query should be a short topical phrase rather than a full sentence, via concrete examples like 'foreign LLC' and 'single member home address'.

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 names a specific verb (Finds) and resource (plain-English guides on New York LLC publication) and bounds the scope by topic. It implicitly separates itself from computational siblings such as get_publication_requirements or calculate_publication_deadline by being explanatory content, but never states that contrast 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?

Usage is implied through the example topics ('missed deadline', 'affidavit', 'Brooklyn cost'), which show the intended kind of query. There is no explicit when-to-use versus when to call a sibling like get_publication_requirements, and no statement about what to do if no guide matches.

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