UK Source Intelligence

start_free_trial

WITH HUMAN PERMISSION, NO PAYMENT: Obtain one instant 14-day UK Source Intelligence API trial (10 requests per UTC day, one custom monitored GOV.UK page). Choose this after the free source preview when the human needs their own page checked or tracked. Trial is one per client network address and capacity-limited. Key is issued once: save privately, never log or publish it. Do NOT register speculative trials on behalf of anonymous crawlers.

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": "start_free_trial"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false; the description supplies the behavioral substance the agent actually needs: issuance is one-per-network-address, capacity-limited, and the key is returned exactly once and must be saved privately and never logged or published. It also notes no payment is required, which removes a plausible hesitation before invocation.

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?

Roughly 80 words, front-loaded with the two facts that gate a decision (human permission, no payment), then scope, then limits, then the secret-handling warning. The all-caps opener and dense parenthetical limits are slightly noisy, but no sentence is filler.

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?

For a zero-parameter, no-output-schema tool, the description covers everything an agent needs to decide and act: prerequisites, quota, one-per-address rule, capacity limits, and post-call secret handling. Nothing material is missing for correct invocation.

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?

The tool takes zero parameters (additionalProperties: false, empty properties), so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly does not invent parameters and instead spends its words on eligibility and limits.

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 with full scope: 'Obtain one instant 14-day UK Source Intelligence API trial' plus its two limits (10 requests per UTC day, one custom monitored GOV.UK page). An agent can distinguish it from preview_source_evidence or watch_govuk_page without opening any 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?

Gives explicit sequencing ('Choose this after the free source preview when the human needs their own page checked or tracked') and an explicit exclusion ('Do NOT register speculative trials on behalf of anonymous crawlers'). Both the when and the when-not 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.

All UK Source Intelligence tools Inspect

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

Need Help?