Skip to main content
Glama

security_sitekey

Read-onlyIdempotent

Get the CAPTCHA site key to embed in your frontend HTML. This is safe to expose publicly — it identifies the widget, not the user.

Example:

{}
// Returns: { "sitekey": "0x..." }

Usage in HTML:

<div class="cf-captcha" data-sitekey="0x..."></div>
<script src="https://your-captcha-provider.example/widget.js" async defer></script>

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnlyHint and idempotentHint, so the safety baseline is set. The description adds genuinely new behavioral context: the key identifies the widget rather than the user, so it is safe to expose publicly, plus an example of the return payload. It stops short of mentioning auth requirements or rate limits, but for a trivial read that is minor.

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 core purpose and the public-safety claim are front-loaded in two sentences. The JSON example earns its place because no output schema exists, but the HTML embedding snippet is somewhat redundant decoration that an agent does not need in order to invoke the tool.

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 description compensates by showing the exact return shape ({"sitekey": "0x..."}), and with zero parameters there is nothing else an agent needs. The definition is complete for a tool of this simplicity.

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, so there is nothing to disambiguate and the baseline of 4 applies. The empty-object example reinforces that no arguments are expected.

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: 'Get the CAPTCHA site key to embed in your frontend HTML.' An agent immediately knows this retrieves a public widget identifier, which is clearly distinct from a review-type sibling like security_review.

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?

The description makes the use case explicit ('embed in your frontend HTML') and clarifies the safety posture ('safe to expose publicly'). It does not name when-not-to-use conditions or alternative tools, but for a single-purpose getter the context is clear enough to route correctly.

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