Loading ToolBench
Well-curated set of 24 focused tools with clear domain (Render platform infrastructure). Strong typed schemas with specific enums and defaults. Descriptions are generally adequate but some are truncated in the schema view. Tool naming is consistent and semantic. No generic 'request_body' parameters detected. The server demonstrates intentional API design rather than auto-generation, with domain-specific patterns (workspace selection, read-only queries, deployment workflows).
Create a new cron job in your Render account. A cron job is a scheduled task that runs on a recurring schedule specified using cron syntax. Cron jobs are ideal for background tasks like data processing, cleanup operations, sending emails, or generating reports. By default, these services are automatically deployed when the specified branch is updated. This tool is currently limited to support only a subset of the cron job configuration parameters. It also only supports cron jobs which don't use Docker, or a container registry. To create a cron job without those limitations, please use the dashboard at: https://dashboard.render.com/create
Create a new Key Value instance in your Render account
Create a new Postgres instance in your Render account
Create a new static site in your Render account. Apps that consist entirely of statically served assets (commonly HTML, CSS, and JS). Static sites have a public onrender.com subdomain and are served over a global CDN. Create a static site if you're building with a framework like: Create React App, Vue.js, Gatsby, etc.This tool is currently limited to support only a subset of the static site configuration parameters.To create a static site without those limitations, please use the dashboard at: https://dashboard.render.com/static/new
Create a new web service in your Render account. A web service is a public-facing service that can be accessed by users on the internet. By default, these services are automatically deployed when the specified branch is updated and do not require a manual trigger of a deploy. The user should only be prompted to manually trigger a deploy if auto-deploy is disabled.This tool is currently limited to support only a subset of the web service configuration parameters.It also only supports web services which don't use Docker, or a container registry.To create a service without those limitations, please use the dashboard at: https://dashboard.render.com/web/new
Minimal descriptions on resource getter/setter tools (update_*, create_* with single serviceId param). Descriptions like 'Create a new Key Value instance' lack context on when/why to use them and what parameters are actually modifiable.
Truncated descriptions in provided schema data (e.g., create_cron_job, create_postgres). Cannot fully assess description quality, but visible portions suggest incomplete context.
Update tools (update_cron_job, update_static_site, update_web_service) accept only 'serviceId' as required parameter - schema does not show what fields can actually be updated. Creates ambiguity about tool capability.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-04-14 | B | 71 | 2025-03-26 | v1 |
Retrieve the details of a particular deploy for a particular service.
Retrieve a Key Value instance by ID
Get performance metrics for any Render resource (services, Postgres databases, key-value stores). Supports CPU usage/limits/targets, memory usage/limits/targets, service instance counts, HTTP request counts and response time metrics, bandwidth usage metrics, database active connection counts for debugging, capacity planning, and performance optimization. Returns time-series data with timestamps and values for the specified time range. HTTP metrics support filtering by host and path for more granular analysis. Limits and targets help understand resource constraints and autoscaling thresholds. Metrics may be empty if the metric is not valid for the given resource.
Retrieve a Postgres instance by ID
Get the currently selected workspace
Get details about a specific service
List deploys matching the provided filters. If no filters are provided, all deploys for the service are returned.
List all Key Value instances in your Render account
List all values for a given log label in the logs matching the provided filters. This can be used to discover what values are available for filtering logs using the list_logs tool. You can query for logs across multiple resources, but all resources must be in the same region and belong to the same owner.
List logs matching the provided filters. Logs are paginated by start and end timestamps. There are more logs to fetch if hasMore is true in the response. Provide the nextStartTime and nextEndTime timestamps as the startTime and endTime query parameters to fetch the next page of logs. You can query for logs across multiple resources, but all resources must be in the same region and belong to the same owner.
List all Postgres databases in your Render account
List all services in your Render account
List the workspaces that you have access to
Run a read-only SQL query against a Render-hosted Postgres database. This tool creates a new connection for each query and closes it after the query completes.
Select a workspace to use for all actions. This tool should only be used after explicitly asking the user to select one, it should not be invoked as part of an automated process. Having the wrong workspace selected can lead to destructive actions being performed on unintended resources.
Update an existing cron job in your Render account.
Update environment variables for a service. By default, environment variables passed in will be merged with the service's existing environment variables. This makes it safe to update environment variableswithout pulling the existing ones into the MCP host's context. To replace all existing environment variables, set the 'replace' parameter to 'true'.
Update an existing static site in your Render account.
Update an existing web service in your Render account.
Inconsistent parameter naming between create and get operations. For example, 'postgresId' in get_postgres but 'postgres' inferred from create_postgres description. Could confuse agents about resource identification.