Skip to main content
Glama
frontalinilucas

saij-mcp

by frontalinilucas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
saij_searchA

Search Argentine legal documents in SAIJ.

Use this tool to find court decisions (fallos), legal summaries (sumarios),
legislation (leyes, decretos), doctrine, and dictámenes from Argentina's
official legal database.

Args:
    query: Search terms (e.g. "consumidor", "phishing bancario").
    doc_type: Type of document to search. Options:
        - "fallo": Court decisions (default)
        - "sumario": Case summaries with thesaurus tags
        - "jurisprudencia": Both fallos and sumarios
        - "legislacion": All legislation
        - "ley": Laws only
        - "decreto": Decrees only
        - "doctrina": Legal doctrine/articles
        - "dictamen": Official opinions
        - "todo": All document types
    field: Search field. "titulo" works with all types. "texto" only
        works with sumarios (searches the summary text body).
    limit: Maximum results to return (1-25, default 10).
    offset: Pagination offset for fetching more results.

Returns:
    JSON with total count, results array, and facet breakdowns
    (by jurisdiction, tribunal, year).
saij_get_documentA

Get a full document from SAIJ by its ID.

Retrieves complete metadata for a court decision, law, or other legal
document, including tribunal, date, jurisdiction, magistrates, and
related sumarios. For fallos, includes PDF download URL.

Args:
    identifier: Either a SAIJ id-infojus (e.g. "FA20000057" for a fallo,
        "LNS0007682" for a law) or the full document UUID.

Returns:
    JSON with complete document metadata. For fallos: tribunal, date,
    case caption (caratula), magistrates, jurisdiction, related sumario
    IDs, and PDF URL. For sumarios: summary text, thesaurus descriptors.
saij_get_sumariosA

Get all legal summaries (sumarios) linked to a court decision.

Each sumario contains a legal principle extracted from the decision,
tagged with thesaurus descriptors. Useful for understanding the key
legal holdings of a case.

Args:
    fallo_id: The fallo's id-infojus (e.g. "FA20000057"). The "FA"
        prefix is added automatically if missing.

Returns:
    JSON with the fallo ID, total count, and array of sumarios, each
    with: summary text, thesaurus descriptors (legal topic tags),
    tribunal, date, and jurisdiction.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

A4.6/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: saij_get_document retrieves a specific document by ID, saij_get_sumarios fetches summaries linked to a court decision, and saij_search performs broad queries across the legal database. There is no overlap in functionality, making tool selection straightforward for an agent.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern with the prefix 'saij_' and a clear verb_noun structure (get_document, get_sumarios, search). This uniformity aids predictability and readability across the tool set.

Tool Count4/5

With 3 tools, the server is slightly lean but reasonable for its purpose of accessing Argentine legal documents. It covers key operations (retrieve, fetch related summaries, search), though a few more tools might enhance coverage without being necessary.

Completeness4/5

The tools provide good coverage for querying and retrieving legal documents, including metadata and summaries. Minor gaps exist, such as lacking explicit update or delete operations, but these are likely unnecessary for a read-only legal database, and agents can work effectively with the provided tools.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources