Skip to main content
Glama

get_checklist

Read-onlyIdempotent

Retrieve a law-specific checklist of applicable rules and code checks to determine whether a product meets requirements such as PDPA readiness.

Instructions

Get a law checklist for the product, for example the PDPA 2027 checklist: the rules of that law that apply to these facts, each with what to look for in the code (look_for) or ask the user (ask). Use it when the user asks whether their project is ready for the PDPA. Send country codes and facts only. Mark each item Found (with file and line), Missing or Can't tell from code; never give a score.

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": {
      "users_in": "<users_in>",
      "facts": "<facts>"
    },
    "name": "get_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
lawNoWhich checklist: 'pdpa'pdpa
factsYesList of the facts that are true, from get_fact_questions
users_inYesISO country codes where users are, as the user said, e.g. ['LK']
company_inNoISO country code where the company (or maker) is, e.g. 'LK'
processing_inNoISO country codes where data is stored or processed

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description explains the output shape and the required marking behavior: each item should be marked Found with file and line, Missing, or Can't tell from code, and never scored. This adds substantial operational context that annotations alone do not provide.

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?

The description is front-loaded with purpose and example, followed by usage and output instructions. It is dense but efficient; nearly every sentence earns its place, though the final output rules are packed into one long instruction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the read-only annotations, full parameter schema coverage, and the presence of an output schema, the description supplies the remaining needed context: trigger, input constraint, and how to mark each returned checklist item. Nothing essential for correct invocation appears 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 description coverage is 100%, so parameter meanings are already well documented. The description adds the useful constraint to send only country codes and facts, but it does not add syntax or meaning beyond what the schema provides.

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 states a specific verb and resource: it retrieves a law checklist for the product and returns applicable rules with look_for/ask guidance. The PDPA example makes the purpose concrete, but it does not explicitly distinguish this tool from siblings such as check_legal_risks or get_rule.

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?

It gives a clear triggering context: use when the user asks whether their project is ready for the PDPA. It also constrains the input to country codes and facts only, but it does not name alternatives or state when not to use this tool.

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