Skip to main content
Glama

search_acts

Find Armenian legal acts in ARLIS by title or content, filter by active status and enactment dates, and return titles, URLs, and metadata for follow-up retrieval.

Instructions

Search ARLIS for acts and return their titles, URLs and metadata. Latest versions only, in ARLIS's default order. Use get_act to retrieve the text. Use only the search_string parameter; others default to what you will need in 99% of cases. Don't use optional parameters without a reason.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default: 5).
activeNoTrue (default): search active or partly active acts only. Use false to include all statuses.
data_afterNoNull (default): no lower bound. Use YYYY-MM-DD to set the earliest ENACTMENT date.
date_beforeNoNull (default): no upper bound. Use YYYY-MM-DD to set the latest ENACTMENT date.
search_stringYesExact string to match inside act titles or, if search_in_text is true, also inside their contents. Case-insensitive; և/եւ/Եւ/ԵՎ normalized.
search_in_textNoFalse (default): search for matches in act TITLES only. Use true to also search act CONTENTS.
incorporations_onlyNoTrue (default): search only incorporations with all amendments included. Use false to also search amendment acts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose meaningful behavior: results are latest-version only, ordered by ARLIS's default sort, and contain metadata rather than full text. It stops short of describing result-count behavior or what happens when limit truncates a large match set, which matters for an unpaginated search tool.

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?

Front-loaded with purpose, then alternatives, then parameter policy — a sensible order. The final two sentences overlap somewhat ("others default to what you will need in 99% of cases" restates "Don't use optional parameters without a reason"), so one could be trimmed.

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 seven parameters, no annotations, and no output schema, the description covers the essentials: what comes back, versioning, ordering, and delegation to get_act. The remaining gap is result-volume behavior (pagination or truncation when many acts match), which an agent would need to plan a search strategy.

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 is 3, but the description adds a genuine usage policy beyond the field docs: treat search_string alone as sufficient in most cases and require a justification for optional parameters. It does not, however, explain interactions between parameters (e.g., search_in_text changing the semantics of search_string).

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 ("Search ARLIS for acts"), names what is returned (titles, URLs, metadata), and narrows scope ("Latest versions only, in ARLIS's default order"). It also explicitly separates itself from the sibling by saying get_act retrieves the text, so an agent can choose without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes full-text retrieval to get_act and gives a concrete operating rule for optional parameters ("Use only the search_string parameter... Don't use optional parameters without a reason"). Both the when-to-use and the when-to-deviate conditions are stated rather than inferred.

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