Skip to main content
Glama

execute

Execute JavaScript code to call and process OVH API endpoints. Use async functions with ovh.request for GET, POST, PUT, DELETE operations.

Instructions

Execute JavaScript against the OVH API. Use 'search' first to find endpoints. Your code must be an async arrow function: async () => { ... } Available:

declare const ovh: {
request(options: {
method: "GET" | "POST" | "PUT" | "DELETE";
path: string;
query?: Record<string, string | number | boolean>;
body?: unknown;
}): Promise<any>;
};

Authentication is automatic. Errors (HTTP >= 400) throw exceptions. Examples:

// List email domains
async () => await ovh.request({ method: "GET", path: "/email/domain" })
// List accounts then get details
async () => {
const accounts = await ovh.request({ method: "GET", path: "/email/domain/example.com/account" });
const details = [];
for (const name of accounts.slice(0, 5)) {
const d = await ovh.request({ method: "GET", path: `/email/domain/example.com/account/${name}` });
details.push(d);
}
return details;
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesJavaScript function to execute.
Behavior5/5

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

With no annotations, the description fully discloses behavior: authentication is automatic, errors throw for HTTP >= 400, code must be an async arrow function, and the exact API signature is provided. No contradictions.

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 relatively long but well-structured with clear sections, code blocks, and examples. Each part serves a purpose; however, some repetition could be trimmed. It is appropriately sized for the complexity.

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?

Given the single required parameter, no output schema, and the complexity of executing arbitrary JavaScript against an API, the description covers all necessary aspects: code format, available objects, authentication, error handling, and usage pattern. It is complete.

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 only parameter 'code' has a schema description but the tool description adds significant value: required format (async arrow function), the available `ovh` object with typed request method, and examples. Since schema coverage is 100%, baseline is 3, but the description elevates it to 4.

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 'Execute JavaScript against the OVH API' and distinguishes from the sibling tool 'search' by instructing to use 'search' first to find endpoints. This provides a specific verb-resource pairing and clear differentiation.

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

Usage Guidelines5/5

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

Explicitly states when to use (after searching) and provides a detailed code template, available API methods, error handling, and examples. It mentions the alternative tool 'search' and gives practical usage guidance.

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