Skip to main content
Glama
Sign In

marketing-compliance

by fi.northpoint
OverviewDiscussionsAdmin

get_regulation

Return one rule from NorthPoint's regulations library by id (e.g. "vara/prior-marketing-approval", "mica/rules/article-66-3-casp-risk-warnings-and-white-paper-links") or by its northpoint.fi URL: citation, summary, section headings, regulator sources and the page URL. Use lookup_regulation first to find the id. No API key required.

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": {
      "id": "<id>"
    },
    "name": "get_regulation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe rule id "<regime>/<slug>" or the page URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly succeeds: "Return one rule" implies a non-mutating read, "No API key required" discloses the auth requirement, and the returned fields are listed. It does not cover failure behavior (unknown id, invalid URL form) or rate limits, which leaves a small gap.

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?

Purpose and identifier forms are front-loaded in the first clause, with examples, return fields, the lookup hint, and the auth note following in compact order. It is a dense single sentence plus two short ones with no filler, though the return-field enumeration 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?

There is no output schema, so the description must describe the return payload, and it does (citation, summary, section headings, regulator sources, page URL). For a one-parameter read tool this is nearly complete; only error/empty-result behavior is unstated.

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% and already documents the single id parameter, so baseline would be 3; the description adds real value by giving two concrete example ids ("vara/prior-marketing-approval", "mica/rules/article-66-3-casp-risk-warnings-and-white-paper-links") and confirming that a page URL is also accepted as input.

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 ("Return one rule from NorthPoint's regulations library") and names the two accepted identifier forms (id or northpoint.fi URL), which cleanly separates it from the sibling lookup_regulation search tool. It also enumerates what the returned rule contains, so an agent knows exactly what it gets.

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?

"Use lookup_regulation first to find the id" gives an explicit routing rule to the alternative tool when the caller lacks an id. It stops short of stating what to do on a bad/missing id or when a full-text search would be preferable, but the core when-to-use condition is unambiguous.

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

All marketing-compliance toolsInspect
Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources