Skip to main content
Glama

search

Query the OVH API specification with custom JavaScript. Discover endpoints, request bodies, and schemas by executing code against the OpenAPI definition.

Instructions

Search the OVH API OpenAPI 3.1 spec. All configured services are included. The spec is passed as argument to your function. Your code must be a function that receives spec and returns a value: (spec) => { ... } Types available:

interface ParameterObject {
name: string; in: "path" | "query"; required: boolean;
description: string; schema: SchemaObject;
}
interface OperationObject {
summary: string; parameters: ParameterObject[];
requestBody?: { content: { "application/json": { schema: SchemaObject } } };
responses: { "200": { content: { "application/json": { schema: SchemaObject } } } };
}
declare function yourCode(spec: {
paths: Record<string, Record<string, OperationObject>>;
components: { schemas: Record<string, SchemaObject> };
}): any;

Examples:

// Find account-related endpoints
(spec) => {
const results = [];
for (const [path, methods] of Object.entries(spec.paths)) {
if (path.includes("/account")) {
for (const [method, op] of Object.entries(methods)) {
results.push({ method: method.toUpperCase(), path, summary: op.summary });
}
}
}
return results;
}
// Inspect a model schema
(spec) => spec.components.schemas["email.domain.Account"]
// Get request body for creating an account
(spec) => {
const op = spec.paths["/email/domain/{domain}/account"]?.post;
return { summary: op?.summary, requestBody: op?.requestBody, parameters: op?.parameters };
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesJavaScript function to execute.
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It explains that the tool executes user-provided JavaScript code against the spec, but it does not mention safety implications, execution limits, or whether modifications are possible. Examples are all read-only, but this is not explicitly stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the purpose and then provides necessary details including types and examples. While it is lengthy, the information is essential for correct usage, so it is not overly verbose.

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

Completeness3/5

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

The description explains how to use the parameter and what the code should do, but it does not describe what the tool returns (e.g., the output format or handling of errors). Given the absence of an output schema, this leaves some ambiguity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, but the description adds extensive detail: the exact function signature, type definitions, and multiple code examples. This far exceeds the schema's simple description of 'JavaScript function to execute.'

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 clearly states 'Search the OVH API OpenAPI 3.1 spec' with a specific verb and resource. It distinguishes from the sibling tool 'execute' by focusing on spec search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool versus the sibling 'execute' or provide any alternatives. It only mentions that all configured services are included, which is implicit context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidlandais/ovh-api-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server