Skip to main content
Glama

Company facts

company_info
Read-onlyIdempotent

Facts about Klarframe: what it does, founders, location, languages, how projects are priced, contact and legal pages.

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

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: de, en, es or it. Defaults to de.de

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description contributes the content scope, which is genuinely useful, but says nothing about return format, whether the facts are static or cached, or how the answer language affects output. That is adequate but not rich for a read tool whose annotations carry the behavioral load.

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 that enumerates coverage with no filler or repetition. Every listed item maps to a plausible user question, so nothing is wasted.

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 zero-required-parameter, single-param read tool with no output schema, the content enumeration effectively serves as a return-value sketch, which is what an agent needs to decide to call it. Minor gap: no statement that the response is static company data or how the lang parameter shapes it.

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 documents its default and accepted values, so the baseline is 3. The description adds no parameter detail and mildly risks confusion: 'languages' in the content list refers to the company's spoken languages, while the lang parameter selects the answer language — the description does not disambiguate these.

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 a concrete resource (Klarframe company facts) and enumerates its coverage: what the company does, founders, location, languages, project pricing, contact and legal pages. That is far more specific than the title alone and makes the tool's domain obvious against siblings like list_products or get_intro_slots. It stops short of explicitly contrasting itself with any sibling, so it lands at 4 rather than 5.

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?

No explicit when-to-use or when-not-to-use statement appears; the guidance is implied by the content list, so an agent can infer 'use for questions about the company, pricing, or legal/contact details'. No alternative tool is named for overlapping needs (e.g., pricing questions vs. list_products), leaving the routing decision to inference.

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