Skip to main content
Glama

Houski Property Data

auth_endpoint

Check that an API key exists and is enabled. Does not bill per call. Returns api_key_authorized boolean. It does not check the key's maximum monthly spend, so a billed tool can still refuse a key that passes here.

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": {
      "api_key": "<api_key>"
    },
    "name": "auth_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYesAPI key to validate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 does well: it discloses that calls are not billed, that the result is an api_key_authorized boolean, and that spend limits are out of scope. It omits what happens for a malformed or unknown key (false vs. error) and whether this endpoint itself requires credentials, which are meaningful gaps for an auth tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the positive statement of purpose, then the billing caveat, then the scope limitation. Every sentence carries distinct information with no filler.

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?

For a single-parameter read-only check with no output schema, the description covers purpose, cost behavior, return field, and the key limitation. The remaining gap is failure/error semantics, which the description leaves unstated.

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?

There is only one parameter and schema description coverage is 100%, so the schema already documents api_key fully. The description adds no format, sourcing, or validation detail for the key, so the baseline of 3 applies.

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: check that an API key exists and is enabled. It also scopes the check precisely by excluding spend-limit validation, so an agent can distinguish it from the billed endpoint tools without inspecting 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the usage context clear: this is a pre-flight key check, not a spend-limit gate, and a billed tool may still reject a key that passes here. It stops short of an explicit 'call this before X, not instead of Y' instruction, but the caveat sentence effectively routes the agent.

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