Skip to main content
Glama

Get memory limit

render_get_memory_limit
Read-onlyIdempotent

Retrieve memory limits for one or more Render resources. Specify service, instance, or resource IDs and optional time range to get memory limit metrics.

Instructions

Get memory limit. Get the memory limit for one or more resources. Calls GET /metrics/memory-limit on the Render Public API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endTimeNoEpoch/Unix timestamp of end of time range to return. Defaults to `now()`.
serviceNoThis parameter is deprecated. Please use `resource` instead (deprecated)
instanceNoInstance ID to query. When multiple instance ID query params are provided, they are ORed together
resourceNoResource ID to query. When multiple resource query params are provided, they are ORed together. Resources can be service ids, Postgres ids, or Redis ids
startTimeNoEpoch/Unix timestamp of start of time range to return. Defaults to `now() - 1 hour`.
resolutionSecondsNoThe resolution of the returned data
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. Description adds the API endpoint called. No further behavioral details beyond schema.

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?

Three sentences, concise. However, the first sentence is redundant with the title. Still mostly efficient.

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?

Adequate for a read tool with 100% schema coverage and no output schema. But lacks description of return format or behavior when no resource is specified.

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 coverage is 100%, so the schema already documents all parameters. The description adds no additional parameter-level meaning.

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 clearly states the tool retrieves memory limits for resources, using a specific verb ('Get'). It distinguishes implicitly from siblings like render_get_cpu_limit, but does not explicitly differentiate.

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?

No guidance provided on when to use this tool versus alternatives. No mention of prerequisites, context, or exclusions.

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/LuSrodri/render-useful-mcp'

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