show_project_overviewUse this when someone wants a quick overview of one of their localization projects. Returns an overview card with the project's default locale, up to 24 configured locales and timestamps. Not for translation completeness.
| Name | Required | Description | Default |
|---|---|---|---|
| projectIdOrName | Yes | Project id or name |
| Name | Required | Description | Default |
|---|---|---|---|
| project | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / projectIdOrName / descriptionPrevious value: -"MultiLocale project id or name (slug) to render"New value: +"Project id or name"Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / additionalPropertiesRemoved value: -falseOutput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Output schema / properties / project / anyOfPrevious value: -[
- {
- "additionalProperties": false,
- "properties": {
- "creationTime": {
- "anyOf": [
- {
- "maxLength": 32,
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "defaultLocale": {
- "anyOf": [
- {
- "maxLength": 35,
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "id": {
- "anyOf": [
- {
- "pattern": "^[0-9a-f]{24}$",
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "lastEditTime": {
- "$ref": "#/properties/project/anyOf/0/properties/creationTime"
- },
- "localeCount": {
- "minimum": 0,
- "type": "integer"
- },
- "locales": {
- "items": {
- "$ref": "#/properties/project/anyOf/0/properties/defaultLocale/anyOf/0"
- },
- "maxItems": 24,
- "type": "array"
- },
- "localesTruncated": {
- "type": "boolean"
- },
- "name": {
- "maxLength": 128,
- "type": "string"
- }
- },
- "required": [
- "id",
- "name",
- "defaultLocale",
- "localeCount",
- "localesTruncated",
- "locales",
- "creationTime",
- "lastEditTime"
- ],
- "type": "object"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "additionalProperties": false,
+ "properties": {
+ "creationTime": {
+ "anyOf": [
+ {
+ "maxLength": 32,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "defaultLocale": {
+ "anyOf": [
+ {
+ "maxLength": 35,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "id": {
+ "anyOf": [
+ {
+ "pattern": "^[0-9a-f]{24}$",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "lastEditTime": {
+ "anyOf": [
+ {
+ "maxLength": 32,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "localeCount": {
+ "maximum": 9007199254740991,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "locales": {
+ "items": {
+ "maxLength": 35,
+ "type": "string"
+ },
+ "maxItems": 24,
+ "type": "array"
+ },
+ "localesTruncated": {
+ "type": "boolean"
+ },
+ "name": {
+ "maxLength": 128,
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "defaultLocale",
+ "localeCount",
+ "localesTruncated",
+ "locales",
+ "creationTime",
+ "lastEditTime"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the capped 24-locale limit and the inclusion of timestamps, which tell the agent what the card will and won't contain.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, trigger first, return shape second, exclusion last. No filler and nothing repeated from the name or schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
A read-only single-param lookup with an output schema and full annotation coverage needs little else. The description supplies the trigger and the one behavioral quirk (24-locale cap), which is sufficient for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for the single projectIdOrName parameter, so the schema already carries its semantics. The description adds no format, lookup, or ambiguity guidance (e.g. id vs. name precedence), so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (show), resource (project overview), and the shape of what comes back (an overview card with default locale, configured locales, timestamps). It also carves out a boundary against the translation-completeness siblings, though it does not name get_project or find_missing_translations directly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives a clear trigger (someone wants a quick overview of one of their localization projects) and an explicit exclusion (not for translation completeness). It stops short of naming the alternative tool an agent should use for completeness queries.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.