Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Check Jobiba AI availability

ai_provider_status
Read-onlyIdempotent

Inspect configured chat and embedding provider readiness without exposing provider credentials or endpoints.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the check reports readiness 'without exposing provider credentials or endpoints', telling the agent the output is safe to surface and what it will not contain.

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 sentence that front-loads the action and scope, with no filler, repetition of the title, or hedging. Every clause earns its place, including the security qualifier.

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 simple, zero-parameter, closed-world diagnostic with full annotation coverage, the definition is nearly complete. The only gap is that it does not describe the shape of the readiness result (for example, per-provider flags), though with no output schema that is a small omission rather than a blocking one.

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, so there is nothing for the description to clarify beyond what the empty object schema already conveys. The baseline for a param-free tool applies, with no gap to compensate for.

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 pairs a specific verb, 'Inspect', with a concrete resource, the readiness of 'configured chat and embedding provider readiness', so the agent knows exactly what is being checked. It is naturally distinct from the career-oriented siblings, though it does not explicitly state any differentiation itself.

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 only implied: an agent can infer this is a diagnostic to run before relying on AI-backed features. There is no explicit statement of when to call it, no prerequisites, and no named alternative, but for a zero-argument status check with no overlapping siblings, that omission is minor.

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.