Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Check the review queue's response times

luca_review_queue_sla
Read-onlyIdempotent

Read median first-response time and daily trend for the review queue to check if it is cleared fast enough.

Instructions

Read median first-response time and its daily trend. Tells you whether the queue is being cleared fast enough.

Luca operation: GET /api/review-queue/sla Required scopes: review_queue:read Required OAuth scope: luca:read; data sensitivity: full_content Does not require idempotency. Use workspaceId or workspaceSlug to override the default workspace configured by environment.

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": "luca_review_queue_sla"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceIdNoOptional Luca workspace id override.
workspaceSlugNoOptional Luca workspace slug override.

Output Schema

NameRequiredDescriptionDefault
resultYes
provenanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower, yet the description adds genuinely useful operational context: the underlying GET endpoint, required scopes (review_queue:read, luca:read), full_content data sensitivity, and that no idempotency key is needed.

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 the core metric and its interpretation in the first two sentences, followed by a compact operational metadata block. Nothing is wasted, though the metadata block is dense enough to slightly dilute the read.

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?

An output schema exists so return values need not be described, annotations carry the safety profile, and the description supplies endpoint, scopes, sensitivity, and workspace-override behavior. An agent has everything needed to call this correctly.

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?

Schema coverage is 100% and both params are documented there, so the baseline is 3. The description adds the meaningful detail that these override the default workspace configured by the environment, which the schema's bare 'Optional Luca workspace id override' does not convey.

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?

States a precise verb and resource: reading median first-response time and its daily trend, with the outcome it informs (whether the queue is cleared fast enough). This clearly separates it from siblings like luca_review_queue_list or luca_review_queue_explain, but it never names or contrasts with any of them explicitly.

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 implies when you'd want the metric ('Tells you whether the queue is being cleared fast enough') and notes how to target a workspace, but gives no explicit when-to-use vs alternatives guidance and no exclusions relative to the many review_queue siblings.

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

Deploy Server

Other Tools