Skip to main content
Glama

Contact BlueNOC

get_company_contact
Read-onlyIdempotent

Who builds BlueNOC and how to reach them: phone, email, address and office hours.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
nameYes
emailYes
phoneYes
addressNo
countryNo
websiteNo
about_pageNo
contact_pageNo
legal_entityNo
office_hoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "about_page": {
      +      "format": "uri",
      +      "type": "string"
      +    },
      +    "address": {
      +      "type": "string"
      +    },
      +    "contact_page": {
      +      "format": "uri",
      +      "type": "string"
      +    },
      +    "country": {
      +      "type": "string"
      +    },
      +    "email": {
      +      "format": "email",
      +      "type": "string"
      +    },
      +    "legal_entity": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "office_hours": {
      +      "type": "string"
      +    },
      +    "phone": {
      +      "type": "string"
      +    },
      +    "website": {
      +      "format": "uri",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "email",
      +    "phone"
      +  ],
      +  "type": "object"
      +}
  2. 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, non-destructive, and closed-world, so the safety profile is fully covered by structured data. The description adds the concrete field set the caller will receive, but since an output schema exists this is largely restating return content rather than adding behavioral context like freshness or sourcing of the contact data.

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 compact sentence that front-loads the purpose and then lists the payload fields; every clause earns its place with no filler or repetition.

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 lookup with rich annotations and an output schema, the description supplies enough to call it correctly and know what comes back. Only marginal gaps remain, such as whether the contact details are authoritative or cached, which are low-stakes for this tool type.

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 confirms an empty object with additionalProperties=false, so there is nothing for the description to disambiguate. Baseline 4 applies for a parameterless tool.

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 gives a specific resource with a clear verb-like framing ('Who builds BlueNOC and how to reach them') and enumerates the returned fields (phone, email, address, office hours). It is clearly a company-contact lookup, distinct from pricing, product overview, and article siblings, though it never explicitly names those siblings to sharpen the boundary.

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?

Usage is implied rather than stated: an agent can infer this is the tool for 'how do I contact BlueNOC' questions. There are no explicit when-not conditions and no mention of alternatives such as list_articles for support-style inquiries, leaving routing 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