Skip to main content
Glama
Sign In

Refora

by ai.refora
OverviewDiscussionsAdmin

List workspaces

list_workspaces
Read-onlyIdempotent

List the workspaces in the connected Refora organization. Call this first: every other workspace tool needs a workspace_id from here.

Use this tool when the user asks about their workspaces, projects, or brands they're monitoring -- phrases like 'what am I tracking', 'list my projects', 'show me my brands', or 'which workspaces do I have'.

Returns: workspace ID, name, primary brand domain, active prompt count, creation date, website, data_source (own_tracking, market_data or none) and a one-line summary for each workspace.

Example question: 'What workspaces do I have set up in Refora?'

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_workspaces"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context that annotations cannot convey: the sequencing dependency (workspace_id is required downstream) and the exact shape of what comes back, including the data_source values. It does not mention result limits or pagination, which is the only remaining gap.

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?

Front-loaded with purpose and the 'call this first' rule, then usage triggers, then returns. The trailing example question largely restates the phrasing list already given, making it mildly redundant, but nothing else is wasted.

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 parameters and no output schema, the description carries the burden of explaining returns and does so field by field (ID, name, domain, prompt count, creation date, website, data_source, summary). Combined with the dependency note, an agent has everything needed to call it and use the result.

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 tool takes zero parameters, so there is nothing to disambiguate; baseline is 4. The description instead spends its space on return-value semantics, which is appropriate for a no-arg call.

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?

States a specific verb and resource ('List the workspaces in the connected Refora organization') and pins down its role as the entry point for the workspace tools. An agent can distinguish it from siblings like get_account or get_prompt_performance without opening any 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?

Explicitly says 'Call this first: every other workspace tool needs a workspace_id from here', which is a hard dependency rule, and gives concrete user phrasings ('what am I tracking', 'list my projects', 'show me my brands') that map natural language to this tool. Alternatives are effectively excluded because this is the prerequisite step.

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

All Refora toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources