Skip to main content
Glama
Sign In
mcp-sudact

mcp-sudact

by atomno-mcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search_fas_decisions

Search Russian FAS decision cards by case number or text, with filters for law, authority, act type, and dates; use returned citations to request full decision text.

Instructions

Карточки базы решений ФАС через /v1/search court_type=fas.

Не обещает полный текст решения. Источник, дата сведений и предупреждения сохраняются. Текст карточки можно запросить через get_citation.

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

Input Schema

NameRequiredDescriptionDefault
lawNo44-ФЗ/223-ФЗ/135-ФЗ/38-ФЗ.
bodyNoОрган ФАС.
limitNo
queryYesТекст или номер дела ФАС.
date_toNoДата карточки по, YYYY-MM-DD.
act_typeNoВид акта ФАС, например решение.
date_fromNoДата карточки с, YYYY-MM-DD.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations present, the description must carry the full behavioral burden, and it does disclose two genuinely useful traits: results are card/metadata records rather than full text, and source, data date and warnings are preserved for provenance. It says nothing about read-only semantics, pagination beyond the limit parameter, or ordering of results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short, front-loaded sentences with no filler; the key limitation about full text is placed early. The endpoint path detail is mildly implementation-facing but still helps scope the call.

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 values need not be described, and the description covers the main trap (results are cards, not full decisions) plus the follow-up tool. Missing only secondary context such as result ordering and behavior on zero hits for a 7-parameter search.

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 description coverage is 86%, so the schema already documents law, body, query, date_from/date_to, act_type and limit. The description adds no further parameter meaning, so the baseline 3 applies.

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 names the resource precisely — records (карточки) of the FAS decisions database — and identifies the underlying endpoint (court_type=fas), which lets an agent distinguish it from a generic case search. The verb is implied by the tool name rather than stated in the description, and the contrast with the sibling search_cases is not spelled out.

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

Usage Guidelines3/5

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

It gives one explicit routing rule: full decision text is not returned here and should be fetched via get_citation. However, there is no guidance on when to pick this over search_cases, no prerequisites, and no note on empty results or when to broaden filters, so usage is only partly implied.

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