Skip to main content
Glama
Sign In

ProprioSign

by com.propriosign
OverviewDiscussionsAdmin

Read a ProprioSign guide

read_guide
Read-onlyIdempotent

Returns the full text of one ProprioSign guide in Markdown, with its official sources. Give the slug or URL returned by search_guides.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage wanted. If missing, the language of the slug or URL.
guideYesSlug or URL of the guide, for example "delais-avis-renouvellement-bail-quebec" or https://propriosign.com/en/guides/quebec-lease-renewal-notice-deadlines.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds value beyond them by disclosing the return shape: full Markdown text with official sources cited, which matters because there is no output schema. It omits failure behavior for an invalid slug and any indication of response size.

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?

Two sentences, no filler, and the payload description is front-loaded before the argument-provenance instruction. Every clause earns its place.

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?

For a simple two-parameter read tool with full annotation coverage, the definition supplies purpose, argument source, and return format. Minor gaps remain around not-found handling and content length, but nothing essential to correct invocation 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 coverage is 100%, with the guide parameter's examples and the lang enum fully documented in the schema. The description only adds provenance for the guide value (it comes from search_guides) and says nothing about the optional lang parameter or its fallback behavior. Baseline 3 is appropriate when the schema already carries the semantics.

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 ('Returns the full text of one ProprioSign guide'), plus the return format (Markdown) and that official sources are included. The word 'one' scopes it to a single item, which cleanly separates it from the sibling search_guides that returns many.

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?

Explicitly tells the agent where the argument comes from ('the slug or URL returned by search_guides'), which establishes the required call sequence. It does not state any when-not-to-use condition or what happens if the slug is unknown, but the usage context is otherwise unambiguous.

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

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