globalize.now

List style guides

list_style_guides

Read-only

List the per-language style guides for a project — which target languages have one, with the guide id and the length of its instructions in characters. The instructions themselves are not included; get_style_guide returns one language's full text. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

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": {
      "project": "<project>"
    },
    "name": "list_style_guides"
  }
}

Input Schema

Name	Required	Description	Default
`project`	Yes	Project id (UUID) or slug

Output Schema

Name	Required	Description	Default
`styleGuides`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 28, 2026

addedOutput schema / properties / styleGuides / items / properties / characterCount

Added value: +{
+  "description": "Length of the instructions, in characters",
+  "type": "number"
+}

removedOutput schema / properties / styleGuides / items / properties / instructions
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / properties / styleGuides / items / required

Previous value: -[
-  "id",
-  "projectId",
-  "targetLanguage",
-  "instructions"
-]New value: +[
+  "id",
+  "projectId",
+  "targetLanguage",
+  "characterCount"
+]

First observedSep 24, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: what the response contains, what it deliberately omits, and a UX rule about presenting names/locales instead of UUIDs.

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 listing behavior, then the return-scope caveat, then the presentation rule. Every sentence carries information, though the UUID-display rule is a presentation convention rather than tool behavior and slightly dilutes focus.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 no explanation, yet the description usefully summarizes the shape anyway. Combined with full schema coverage and read-only annotations, an agent has everything needed to call it correctly.

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% and the single 'project' parameter is fully documented in the schema as id or slug. The description adds nothing about the parameter itself, so the baseline of 3 applies.

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 per-language style guides for a project') and immediately scopes the payload: which languages have one, the guide id, and the instruction length. It is clearly distinguishable from get_style_guide, which it names.

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 routes the agent: this tool returns metadata only because 'the instructions themselves are not included', and get_style_guide returns one language's full text. That is a named alternative plus the condition that selects it.

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

All globalize.now tools Inspect

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.