Skip to main content
Glama

globalize.now

by io.github.globalize-now
OverviewDiscussionsAdmin

List projects

list_projects
Read-only

List all projects in your organisation — each project's id, slug and name with the id, name and locale of its source and target languages. get_project returns the full project. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedOutput schema / properties / projects / items / properties / context
      Removed value: -{
-  "description": "Project-wide translation context; null when unset",
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • removedOutput schema / properties / projects / items / properties / orgId
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / properties / projects / items / properties / sourceLanguage / anyOf
      Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "id": {
-        "description": "project_language id — what the glossary and style-guide tools key on",
-        "type": "string"
-      },
-      "isSource": {
-        "type": "boolean"
-      },
-      "languageId": {
-        "description": "Catalog language id, null for a locale not in the catalog",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "locale": {
-        "type": "string"
-      },
-      "name": {
-        "type": "string"
-      },
-      "pathLocale": {
-        "description": "Spelling this locale takes in repository paths, when it differs",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "projectId": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "projectId",
-      "name",
-      "locale",
-      "isSource"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "id": {
+        "description": "project_language id — what the glossary and style-guide tools key on",
+        "type": "string"
+      },
+      "locale": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "locale"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / projects / items / properties / targetLanguages / items / properties / isSource
      Removed value: -{
-  "type": "boolean"
-}
    • removedOutput schema / properties / projects / items / properties / targetLanguages / items / properties / languageId
      Removed value: -{
-  "description": "Catalog language id, null for a locale not in the catalog",
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • removedOutput schema / properties / projects / items / properties / targetLanguages / items / properties / pathLocale
      Removed value: -{
-  "description": "Spelling this locale takes in repository paths, when it differs",
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • removedOutput schema / properties / projects / items / properties / targetLanguages / items / properties / projectId
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / properties / projects / items / properties / targetLanguages / items / required
      Previous value: -[
-  "id",
-  "projectId",
-  "name",
-  "locale",
-  "isSource"
-]New value: +[
+  "id",
+  "name",
+  "locale"
+]
    • changedOutput schema / properties / projects / items / required
      Previous value: -[
-  "id",
-  "orgId",
-  "name",
-  "slug",
-  "sourceLanguage",
-  "targetLanguages"
-]New value: +[
+  "id",
+  "slug",
+  "name",
+  "sourceLanguage",
+  "targetLanguages"
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world scope, so safety is covered. The description adds value beyond that with the exact shape of the returned summary and the rule that UUIDs are for tool calls only. It does not mention pagination or result-set limits for an organisation-wide listing, which is the 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 the action and return fields, then the sibling distinction, then the id-vs-name convention. The third sentence is slightly tangential to tool invocation but still earns its place by preventing UUID leakage in user replies.

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-value documentation is not required, yet the description still summarises it usefully. Combined with the sibling contrast and the presentation convention, it is complete enough for a zero-parameter read tool; only pagination/scale behaviour is unaddressed.

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?

Zero parameters, so the baseline of 4 applies. There is nothing in the schema for the description to clarify or contradict, and no missing parameter documentation to compensate for.

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+resource ("List all projects in your organisation") and enumerates the returned fields (id, slug, name, plus source/target language id/name/locale). It distinguishes itself from the closest sibling by noting get_project returns the full project.

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: use this for the list, use get_project when the full project is needed. It also gives an output convention for the user-facing reply (use name and locale, never ids), which is actionable guidance rather than inference.

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

All globalize.now 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