Skip to main content
Glama
Sign In
maharashtra-courts-drafting

maharashtra-courts-drafting

by edenbuilds
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_reference_note

Read-onlyIdempotent

Load packed reference guides covering getting-started, harness, territorial-jurisdiction, acronyms, court-fees-stamp, efiling, and install docs for drafting court-ready pleadings.

Instructions

Load a packed reference.

Names: getting-started, harness, territorial-jurisdiction, acronyms, court-fees-stamp, efiling. Also accepts docs/INSTALL or docs/HARNESS.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds the list of valid names and alternative paths, which is useful context but not deep behavioral detail like error handling or return behavior.

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: a one-line purpose followed by a flat list of valid values. No wasted words, and the purpose is front-loaded.

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?

With a single parameter, an output schema present, and the description listing all valid inputs, the tool is almost fully specified. Minor gaps remain (e.g., behavior on invalid names), but the description is adequate for correct invocation.

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?

The schema has one parameter 'name' with zero description coverage. The description fully compensates by enumerating all valid names ('getting-started', 'harness', etc.) and alternative path forms ('docs/INSTALL', 'docs/HARNESS'), providing crucial semantic meaning beyond the schema.

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 states a clear verb ('Load') and resource ('packed reference'), and the name 'get_reference_note' aligns. It doesn't explicitly distinguish from siblings like get_template, but the resource type is unique enough that an agent can infer the tool's role.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus the many sibling tools. The description lists valid names but doesn't explain scenarios where this tool is preferred over alternatives, nor any exclusions or prerequisites.

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

Deploy Server

Other Tools