HostVeritas Hosting Research

Get Provider

get_provider

Read-onlyIdempotent

Read one published provider by canonical slug. Returns public facts, evidence, explicit unknowns, approximate signup and renewal ranges, published-review aggregates and eligible endpoint uptime. Existing public field entitlements apply. Editorial availability is separate from customer reviews. Missing and hidden profiles return the same unavailable result.

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": {
      "slug": "<slug>"
    },
    "name": "get_provider"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes

Output Schema

Name	Required	Description	Default
`provider`	Yes
`warnings`	Yes
`retrieved_at`	Yes
`schema_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnly, idempotent, and non-destructive annotations, it discloses the kinds of public facts returned, the presence of evidence and explicit unknowns, approximate signup/renewal ranges, review aggregates, uptime, entitlement-limited fields, and that editorial availability is separate from customer reviews. These are meaningful behavioral constraints an agent would not otherwise know.

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?

The purpose is front-loaded and followed by compact details about returned content, entitlement constraints, and missing/hidden behavior. Every sentence contributes useful information with no repetition or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with annotations and an output schema, the description supplies sufficient context: what it reads, what it returns at a high level, entitlement limitations, and how missing/hidden profiles behave. No critical invocation or interpretation gap remains for its complexity.

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?

The only parameter is slug, and the description adds that it is a canonical slug identifying a published provider. However, with 0% schema description coverage, it does not restate the lowercase-hyphen pattern or length limit, leaving the exact canonical format to the schema.

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 states a specific verb and resource: 'Read one published provider by canonical slug.' The word 'one' and the slug selector clearly distinguish this from list/search or comparison siblings such as search_providers and compare_providers.

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?

It establishes a clear usage context: fetch a single provider when you already have its canonical slug, with missing and hidden profiles returning the same unavailable result. It does not explicitly name the sibling alternatives or explain how to obtain a slug, so it lacks full when-to-use routing but is not vague.

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

All HostVeritas Hosting Research tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?