Skip to main content
Glama

BlackLabel Tech Website MCP

site_info

Read-onlyIdempotent

What BlackLabel Tech (blacklabeltec.com) is, with links to its sitemap, docs, contact and every discovery document.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds value by disclosing the shape of the returned content (links to sitemap, docs, contact, discovery documents), which matters since there is no output schema, but it says nothing about size, pagination or freshness of that link set.

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?

A single front-loaded sentence with no filler; the core identity of the resource comes first and the link inventory follows as supporting detail. Nothing would be lost or gained by rewording it.

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 parameterless, read-only tool with no output schema, the description supplies the essential expectation of what comes back and needs no more to be callable. The only shortfall is the absence of any statement about when this is preferable to read_page or search_pages.

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 and the schema is a closed empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter meaning is missing.

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 names the specific resource (BlackLabel Tech / blacklabeltec.com) and states the payload: an 'about' overview plus links to sitemap, docs, contact and every discovery document. It is clear what the tool returns, but it never explicitly contrasts itself with read_page or search_pages, leaving the sibling boundary to be inferred from the word 'discovery document'.

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?

There is only implied guidance. Phrasing like 'every discovery document' hints that this is the indexing/entry-point tool to call before read_page or search_pages, but no explicit condition ('use this first to find a page, then use read_page') or exclusion is stated.

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