Skip to main content
Glama

Andrii Co. Notary & Apostille Assistant

by net.andrii
OverviewDiscussionsAdmin

search_documentation

Read-only

Search the text of andrii.co — every service page, the terms and privacy notices, and the 110-jurisdiction apostille handbook (who issues an apostille, accepted documents, forms, offices, fees, payment). Use for reference questions the other tools do not answer, and to cite a page. Accepts: query (keywords, not prose — there is no semantic matching), optional lang, section, limit. Returns ranked page excerpts with a URL and a Markdown URL to read in full; no match is an empty list. Reference text, not a live quote — use get_price_quote and check_service_area for what we charge and where we go.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoRestrict to one language. Only `en` is indexed today; any other value returns no results rather than silently ignoring the filter.
limitNoHow many results (default 10, max 20).
queryYesWhat to look for. Keywords beat prose: this is a lexical index with no semantic fallback, so "mail-in apostille birth certificate" finds the page that "can I post my documents instead" does not.
sectionNoRestrict to sections whose heading contains this text (e.g. "What it costs"). Heading TEXT, not a URL fragment — the pages carry no anchors.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
countYes
queryYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "note": {
+      "type": "string"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "properties": {
+          "excerpt": {
+            "type": "string"
+          },
+          "markdownUrl": {
+            "description": "Markdown twin of the page — fetch to read it in full.",
+            "type": "string"
+          },
+          "section": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "description": "Canonical page URL to cite.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "url",
+          "markdownUrl",
+          "excerpt"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "count",
+    "results",
+    "note"
+  ],
+  "type": "object"
+}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already convey read-only and non-destructive behavior. The description adds meaningful behavioral detail beyond that: lexical matching with no semantic fallback, returns ranked excerpts with a URL and Markdown URL, empty list on no match, and the caveat that this is reference text, not a live quote. No contradiction with annotations.

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?

Five dense sentences, each earning its place: scope first, usage next, params, return behavior, and exclusions. No filler or repetition; the most important scoping information is front-loaded.

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?

Covers purpose, content scope, usage context, parameter constraints, return behavior, and distinctions from siblings. With an output schema present and annotations covering safety, nothing an agent needs to decide when and how to call it is missing.

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 the baseline is 3. The description reinforces that query should be keywords and mentions optional lang, section, and limit, but it does not add new semantic information beyond what the schema already provides. The 'keywords, not prose' emphasis is helpful but redundant with the schema's own guidance.

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: 'Search the text of andrii.co', enumerating content (service pages, terms, privacy notices, apostille handbook). It distinguishes itself from siblings by saying it is for 'reference questions the other tools do not answer' and explicitly names get_price_quote and check_service_area as alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use this tool: 'Use for reference questions the other tools do not answer, and to cite a page.' It also provides a clear exclusion: 'not a live quote — use get_price_quote and check_service_area for what we charge and where we go.'

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

All Andrii Co. Notary & Apostille Assistant 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