Skip to main content
Glama

execute_rest_call

Execute REST API calls to Teradata cloud services with custom authentication, Socks5 proxy, and multipart file uploads.

Instructions

Execute a REST API call with support for custom auth, Socks5 proxy, and multipart uploads. Use get_service_config to see available base URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull URL to the REST endpoint
authNoAuthentication config. Omit to use session auth if set. Example: {"type": "bearer", "token": "..."} or {"type": "basic", "username": "...", "password": "..."}
bodyNoRequest body (JSON object or string)
filesNoFiles to upload (multipart). Key is field name, value is {"path": "/path/to/file"}
proxyNoProxy config. Example: {"type": "socks5", "host": "localhost", "port": 1080}
methodYesHTTP method
headersNoCustom HTTP headers (e.g., {"X-API-Key": "value"})
timeoutNoRequest timeout in milliseconds (default: 30000)
formDataNoForm fields as key-value pairs (string, number, or boolean values)
filePatternNoGlob pattern to match files (e.g., /tmp/*.pdf, ~/docs/**/*.csv). Alternative to explicit files.
validateStatusNoIf true, non-2xx responses throw error. If false (default), all responses succeed.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses high-level features (custom auth, proxy, multipart) but does not detail side effects, limitations, error handling, or performance behaviors beyond what is in the schema.

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 description is two sentences long, front-loads the core purpose, and contains no extraneous information. Every sentence earns its place.

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

Completeness2/5

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

Despite the tool's complexity (11 parameters, no output schema), the description is very brief. It omits critical context such as response format, dependency on setup tools (set_auth, set_proxy), and typical use cases. Missing information that would help an agent use the tool correctly.

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?

Schema description coverage is 100%, so baseline is 3. The description adds a hint about using get_service_config for base URLs, which relates to the url parameter, but does not add significant meaning beyond the schema's parameter descriptions.

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 the verb 'Execute' and resource 'REST API call', and distinguishes from siblings by listing unique features like custom auth, proxy, and multipart uploads. It also directs to get_service_config for base URLs, which differentiates its use.

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?

The description mentions use of get_service_config to see base URLs, implying a prerequisite, but does not explicitly state when to use this tool versus alternatives or when not to use it. No exclusions or context for sibling tools are provided.

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/ksturgeon-td/tdrest-mcp'

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