Skip to main content
Glama

Align's published facts

align_facts
Read-only

What Align publishes about itself, each row with the alignlabs.dev page it comes from: the company and its FINTRAC registration, the four account currencies and their rails, the stablecoins and networks accepted, conversion and the OTC desk, rail timings, who can open an account, how pricing works (by quote, no fees listed) and AlignConnect. Optionally return one section.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "align_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionNoOnly this section

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral value beyond that: it discloses that results are row-shaped with source-page provenance ('each row with the alignlabs.dev page it comes from') and that the content is self-reported published material rather than computed data. It does not say whether content is cached or how current it is, which keeps it out of the top band.

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?

It is a single front-loaded sentence that identifies the resource and its provenance before enumerating sections. The enumeration is long but earns its place because no output schema exists, so it is the only signal of what comes back. Minor cost is that the parenthetical '(by quote, no fees listed)' is a content detail embedded in a list rather than a stated limitation.

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?

With no output schema, the enumeration of the eight returned topics and the source-page provenance does the work the missing output schema cannot. Combined with fully covered input schema and read-only annotations, an agent has enough to decide to call it and to predict the response shape. Nothing material is missing for a single-optional-parameter read tool.

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% and the single enum parameter is fully self-documenting, so the baseline is 3. The description's 'Optionally return one section' confirms the parameter is optional and narrows scope to a single section, but adds no format or interaction detail beyond the schema. With one parameter and complete schema coverage, the schema carries the semantic load.

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 opens with a concrete framing: it returns 'What Align publishes about itself, each row with the alignlabs.dev page it comes from,' then enumerates the specific topics covered (FINTRAC registration, currencies/rails, stablecoins, conversion/OTC, timings, eligibility, pricing, AlignConnect). That topic list makes it distinguishable from siblings like stablecoin_rate or plan_offramp, which handle operational rather than published reference content. It stops short of naming a sibling as an alternative, so it is clear but not fully differentiated.

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?

Usage is only implied: an agent can infer this is the tool for static, self-published reference facts about Align rather than live rate or transfer operations. There is no explicit 'use this when…' or 'use X instead when…' guidance, and no mention of prerequisites or freshness. The only usage-direction sentence is 'Optionally return one section,' which guides parameter use rather than tool selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources