Skip to main content
Glama
Sign In
conformi-search

conformi-search

Official
by conformi-eu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_knowledge_article

Read-only

Retrieve a pre-generated knowledge report for any EU legal act using its CELEX number, including legal status date metadata and primary-source citations from EUR-Lex.

Instructions

Pre-generated knowledge report for one EU legal act (CELEX number), including Rechtsstand (legal-status date) metadata. Free — no API key required. Research tool with primary-source citations (CELEX/EUR-Lex) — not legal advice, no attorney-client relationship.

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

Input Schema

NameRequiredDescriptionDefault
celexYesCELEX number, e.g. 32024R1689 (AI Act)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark readOnlyHint true. Description adds value by noting it's free, requires no API key, pre-generated, and not legal advice, which are behavioral traits not covered by annotations.

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 redundancy. First sentence states core purpose and content; second adds free usage and disclaimer. Every word serves a purpose.

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?

Given one parameter, no output schema, and ample annotations, description sufficiently explains tool purpose, parameter meaning, output type, and behavioral context. Could briefly mention output format (e.g., whether text or URL) but still complete enough.

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 provides pattern and example for celex parameter (100% coverage). Description enhances by clarifying it's 'for one EU legal act' and that output includes Rechtsstand metadata, adding context beyond schema.

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?

Clearly states it provides a pre-generated knowledge report for one EU legal act using a CELEX number, including Rechtsstand metadata. Distinguishes from sibling tool 'get_legal_timeline' by focusing on report content rather than timeline.

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?

Implies usage for research via 'Research tool' and 'Free — no API key required', but does not explicitly contrast with sibling or specify when not to use. No direct guidance on alternatives.

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