Skip to main content
Glama

Emboss

by io.github.edwinorange
OverviewDiscussionsAdmin

Find a blank government form

find_form
Read-onlyIdempotent

Find a blank government form in the Emboss library by name or number, ready to fill. Search the library of blank US federal forms by name, number or alias (w9, W-9, form w 9 and taxpayer identification all find the same form). Returns each match's slug, title, agency, revision and page count. Send the whole query once, and do not search as the user types: each search spends one of the account's rate-limit slots. Up to 20 matches come back at a time (limit sets up to 50); when next_cursor is set, pass it as cursor for the next ones. Pass a slug as create_form's library argument to start from that form. Free.

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
cursorNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Cursor"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 20,
+  "title": "Limit",
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "IRS Form W-9 request for taxpayer identification number"
+  }
+]
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description goes well beyond that: each search consumes a rate-limit slot, up to 20 matches per call with limit up to 50, next_cursor must be echoed as cursor, and the call is free — all operational traits not present in any structured field.

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

Conciseness4/5

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

Front-loaded with the core search purpose, then aliasing behavior, then rate-limit and pagination constraints, then the create_form handoff. Dense but each sentence carries distinct information; only the trailing 'Free.' is borderline filler, and the parenthetical alias examples are slightly verbose.

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

Completeness5/5

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

An output schema exists, so the description's brief list of returned fields is a bonus rather than a necessity. Combined with rate-limit, pagination and handoff details, an agent has everything needed to invoke this correctly and chain it into create_form.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the load and it does: query accepts name, number or alias with a w9/W-9/word-spaced illustration, limit defaults to 20 and caps at 50, and cursor is tied to the returned next_cursor. All three parameters gain meaning absent from the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Find a blank government form in the Emboss library') and clarifies it is a search over blank US federal forms by name, number or alias. That distinguishes it from siblings like get_form, read_form, list_forms and create_form without the agent needing to open any schema.

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 concrete invocation guidance: send the whole query once, do not search as the user types, and pass a resulting slug to create_form's library argument. What is missing is an explicit contrast with list_forms (browsing the whole catalog) or get_form (fetching one known form), which would have made the routing complete among 25 siblings.

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

All Emboss toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources