Skip to main content
Glama
Sign In

Roar AI

by com.roar-ai
OverviewDiscussionsAdmin

Re-read an app's database schema

refresh_app_database_schema
Idempotent

Take a FRESH reading of a hosted app's tables and columns. Returns immediately with a runId; poll get_query_result for it, then call get_app_database_schema. Only needed when no reading is held or the app's schema has changed since — a stored reading is free and this is not.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "appId": "<appId>"
    },
    "name": "refresh_app_database_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesThe app id returned by deploy_app or list_apps

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / appId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Discloses the asynchronous contract that annotations cannot express: it returns immediately with a runId, requires polling get_query_result, then a follow-up get_app_database_schema. It also flags the cost asymmetry versus the free stored read. Nothing here contradicts readOnlyHint=false/idempotentHint=true — a refresh re-reads and stores — so the annotations and prose are consistent.

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?

Two sentences, front-loaded with the action, then the execution sequence, then the cost trade-off. No filler, and the most decision-relevant constraint (needed only when stale) lands before the agent commits.

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?

With no output schema, the description carries the return contract itself (runId plus the polling chain) and the cost model — exactly the context an agent needs to call it correctly in a multi-step flow.

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?

The single appId parameter is already fully documented in the schema (100% coverage, including its origin from deploy_app or list_apps), so the description adds nothing parameter-specific. Per the high-coverage baseline, a 3 is appropriate.

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?

"Take a FRESH reading of a hosted app's tables and columns" is a specific verb plus resource, and the emphasis on FRESH immediately differentiates it from the cached-read sibling get_app_database_schema. An agent knows exactly what this does without opening the schema.

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?

Explicit when-to-use ("Only needed when no reading is held or the app's schema has changed since") and when-not ("a stored reading is free and this is not"), naming the cheaper alternative implicitly via the stored-reading path. The condition that selects this tool over the cached read is stated outright.

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

All Roar AI toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources