globalize.now

Detect repository i18n structure

detect_repository

Read-only

Scan a GitHub repository to detect its framework, locale path patterns, source/target languages, and file format. Use the result to inform create_project and set_repository_patterns. Use the numeric installationId from list_github_installations.

Input Schema

TableJSON Schema

Name	Required	Description
`repo`	Yes
`owner`	Yes
`branch`	No	Branch to scan — normally the primary branch (the first of the watched branches the repository is, or will be, connected with). Defaults to the repository's default branch.
`installationId`	Yes	GitHub App installation id

Output Schema

TableJSON Schema

Name	Required	Description
`preset`	Yes
`message`	No	What was found instead, when nothing was detected
`detected`	Yes	Whether any locale files were found to configure
`appGroups`	No
`framework`	No
`fileFormat`	Yes
`namespaces`	No
`matchedFiles`	No
`scoredPresets`	Yes
`sourceLanguage`	Yes	null when no locale file was found
`discoveredFiles`	Yes
`localeSpellings`	No
`targetLanguages`	Yes
`localePathPatterns`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

addedInput schema / properties / branch

Added value: +{
+  "description": "Branch to scan — normally the primary branch (the first of the watched branches the repository is, or will be, connected with). Defaults to the repository's default branch.",
+  "minLength": 1,
+  "type": "string"
+}

Changed5 schema fields changedSep 28, 2026

addedOutput schema / properties / detected

Added value: +{
+  "description": "Whether any locale files were found to configure",
+  "type": "boolean"
+}

addedOutput schema / properties / message

Added value: +{
+  "description": "What was found instead, when nothing was detected",
+  "type": "string"
+}

addedOutput schema / properties / sourceLanguage / description
```
Added value: +"null when no locale file was found"
```

changedOutput schema / properties / sourceLanguage / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / required

Previous value: -[
-  "scoredPresets",
-  "preset",
-  "sourceLanguage",
-  "targetLanguages",
-  "localePathPatterns",
-  "fileFormat",
-  "discoveredFiles"
-]New value: +[
+  "scoredPresets",
+  "preset",
+  "sourceLanguage",
+  "targetLanguages",
+  "localePathPatterns",
+  "fileFormat",
+  "discoveredFiles",
+  "detected"
+]

First observedSep 24, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that scanning targets a repository and that the output is meant to drive downstream configuration, but says nothing about rate limits, scan duration, private-repo permission requirements, or failure modes on inaccessible branches.

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?

Three short sentences, front-loaded with the action and its outputs, then usage and prerequisite. No filler or restatement of the title.

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. Given a read-only, open-world scan tool, the description covers purpose, prerequisite, and downstream consumption adequately for an agent 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 50%, so the description is expected to compensate for the undocumented parameters. It does add that installationId must be the numeric id from list_github_installations, which is genuinely useful, but owner/repo and branch semantics are left entirely to the schema, so the gap is only partially filled.

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 (scan) and resource (GitHub repository) plus the exact outputs detected: framework, locale path patterns, languages, file format. It also names the sibling tools the result feeds (create_project, set_repository_patterns), so an agent can place it in the workflow without reading other definitions.

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 when to use the result (to inform create_project and set_repository_patterns) and where the required installationId comes from (list_github_installations, numeric id). This is actionable routing guidance, not just implied context.

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.