Skip to main content
Glama
Sign In
100Hires MCP Server

100Hires MCP Server

Official
by 100Hires
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

hires_get_billing

Retrieve billing capability flags for your current company to identify which paid features are available before calling paid-only API endpoints.

Instructions

Get billing/pricing capability flags for the current company. Use before invoking paid-only API behaviors.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden of disclosing behavior. It clearly indicates a read-only operation ('Get') and provides useful context that this is a prerequisite check for paid features. It does not detail error handling or return format, but for a simple flag getter this is reasonable.

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?

Two short sentences with no waste. The first states the action and resource, the second gives usage guidance. Information is front-loaded and every sentence earns its place.

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?

The tool is very simple (no params, no output schema). The description explains what it does and when to use it, making it essentially complete. A slight gap is the lack of detail on returned flags, but that is not critical for invocation.

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 has 0 parameters, and the input schema is an empty object. The baseline for 0 params is 4, and the description adds no param info (not needed).

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?

The description uses a specific verb ('Get') and resource ('billing/pricing capability flags for the current company'), clearly distinguishing this tool from all sibling tools, none of which mention billing or pricing.

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 explicitly states when to use this tool: 'Use before invoking paid-only API behaviors.' This provides clear context, though it does not mention alternatives or exclusions (which are unnecessary given the tool's unique purpose).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools