Skip to main content
Glama
Sign In

Parksy

by com.parksy.mcp
OverviewDiscussionsAdmin

Sample Appeal Letters

sample_letters
Read-onlyIdempotent

Lists Parksy sample letters for appealing a parking ticket (for example broken meter, not the driver, sold the car, paid but still fined, public holiday, apology), or returns the text of one letter with its page and PDF/TXT download links. Templates to adapt, not legal advice.

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

Input Schema

NameRequiredDescriptionDefault
letter_idNoOmit to list all letters. Give an id from the list to get that letter.

Output Schema

NameRequiredDescriptionDefault
urlNo
noteNo
titleNo
letterNo
lettersNo
letter_idNo
disclaimerNo
how_to_useNo
download_pdfNo
download_txtNo
appeal_calculatorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "appeal_calculator": {
+      "type": "string"
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "download_pdf": {
+      "type": "string"
+    },
+    "download_txt": {
+      "type": "string"
+    },
+    "how_to_use": {
+      "type": "string"
+    },
+    "letter": {
+      "type": "string"
+    },
+    "letter_id": {
+      "type": "integer"
+    },
+    "letters": {
+      "items": {
+        "properties": {
+          "letter_id": {
+            "type": "integer"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real context beyond that: the single-letter mode returns page text plus PDF/TXT download links, and the content is adaptable templates rather than advice. It does not discuss list ordering or size, but that is minor for a static reference set.

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?

A single front-loaded sentence covers both modes and the examples, followed by a one-line scope caveat. Nothing is padded and the primary behavior arrives first.

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?

An output schema exists, so return structure need not be documented, yet the description still flags the page text and download links that matter to a caller. For a one-optional-parameter read tool this is essentially complete; only list-size or pagination behavior is left unstated.

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 the baseline would be 3. The description nevertheless reinforces the semantics of letter_id by framing the tool as dual-mode — omitted yields the full list, a listed id yields one letter with its links — which explains the consequence of the parameter rather than just its type.

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?

Names two specific verbs (lists, returns) tied to a concrete resource (Parksy sample appeal letters) and enumerates the letter categories, so an agent knows exactly what comes back in each mode. It also carves out a boundary from the sibling fine_appeal_check by stating these are 'templates to adapt, not legal advice.'

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 implies the two usage modes (browse the list vs. fetch a single letter) and the disclaimer clarifies it is not a legal-advice tool, which helps route against fine_appeal_check. It stops short of an explicit 'use this instead of X when Y' statement, so no exclusion is spelled out.

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

All Parksy 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