Andrii Co. Notary & Apostille Assistant

get_services

Read-only

List the service catalog — Washington notary and apostille offerings with USD prices and accepted payment options (e.g. card, PayPal, Venmo, cash). Optional — the server instructions already summarize the flow; use when the customer asks what we offer or how to pay. Takes: no arguments. Returns services plus payment notes — a static catalog (no error if repeated).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`business`	Yes
`location`	No
`services`	Yes
`languages`	No
`priceMatch`	No
`priceQuote`	No	Which tool gives an exact figure.
`paymentNote`	Yes
`serviceArea`	Yes
`paymentOptions`	Yes
`remoteOnlineNotarization`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Static service catalog, coverage summary and accepted payment options.",
+  "properties": {
+    "business": {
+      "type": "string"
+    },
+    "languages": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "location": {
+      "type": "string"
+    },
+    "paymentNote": {
+      "type": "string"
+    },
+    "paymentOptions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "priceMatch": {
+      "type": "string"
+    },
+    "priceQuote": {
+      "description": "Which tool gives an exact figure.",
+      "type": "string"
+    },
+    "remoteOnlineNotarization": {
+      "type": "boolean"
+    },
+    "serviceArea": {
+      "type": "string"
+    },
+    "services": {
+      "items": {
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "business",
+    "serviceArea",
+    "paymentOptions",
+    "paymentNote",
+    "services"
+  ],
+  "type": "object"
+}

First observedJul 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already signal read-only and non-destructive behavior. The description adds that this is a static catalog with no error if repeated, which conveys idempotency, and states the return shape (services plus payment notes). This is useful beyond the annotations, though it does not detail response structure further.

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?

The description is compact and front-loaded: purpose, then usage context, then I/O and behavior. Every sentence earns its place, and the note about the server instructions is an efficient way to manage optional invocation.

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?

Given the zero-parameter, read-only, static nature of this tool and an existing output schema, the description covers all necessary decision points: when to call it, what it returns, and that repeated calls are harmless. Nothing important 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?

The tool has zero parameters, and the schema shows an empty properties object, so the baseline is 4. The description reinforces this with 'Takes: no arguments,' leaving no ambiguity for the agent.

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?

The description begins with the specific verb 'List' and a concrete resource: the service catalog for Washington notary and apostille offerings, including prices and payment options. This clearly distinguishes it from siblings like get_price_quote, which targets a specific quote, and get_apostille_requirements, which targets requirements.

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?

The description explicitly says to use it when the customer asks what the business offers or how to pay, and notes the tool is optional because server instructions already summarize the flow. It provides clear trigger conditions but does not name alternatives or give explicit when-not-to-use exclusions.

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 tools Inspect

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

Need Help?