Apply a reviewed source-backed path correction to an expected revision. Requires current publisher control or moderator authority. Returns the new revision and reassessment job. Requires the connected identity and community:comment. Preserve request_id and payload on retries.
| Name | Required | Description | Default |
|---|---|---|---|
| request_id | Yes | ||
| replacement | No | ||
| suggestion_id | Yes | ||
| expected_path_revision | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / replacement / properties / metadata / properties / actions / items / properties / bindingsAdded value: +{
+ "description": "Documented task-to-argument mappings. Path arguments replace {argument} in request.url.",
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "argument": {
+ "maxLength": 100,
+ "minLength": 1,
+ "type": "string"
+ },
+ "format": {
+ "default": "raw",
+ "enum": [
+ "raw",
+ "date",
+ "datetime",
+ "year",
+ "lower",
+ "upper",
+ "comma_list",
+ "slug"
+ ],
+ "type": "string"
+ },
+ "location": {
+ "enum": [
+ "path",
+ "query",
+ "body",
+ "tool_argument"
+ ],
+ "type": "string"
+ },
+ "requirement": {
+ "enum": [
+ "doi",
+ "npm_package",
+ "repository",
+ "country_code",
+ "country_name",
+ "year",
+ "date_from",
+ "date_to",
+ "window_start",
+ "window_end",
+ "min_magnitude",
+ "location",
+ "search_keywords",
+ "currency_base",
+ "currency_quotes",
+ "source_language",
+ "target_language",
+ "limit"
+ ],
+ "type": "string"
+ },
+ "template": {
+ "description": "Documented value syntax, e.g. from_publication_date:{value}. Bindings sharing a query argument are comma-joined.",
+ "maxLength": 200,
+ "minLength": 3,
+ "pattern": "\\{value\\}",
+ "type": "string"
+ }
+ },
+ "required": [
+ "requirement",
+ "argument",
+ "location"
+ ],
+ "type": "object"
+ },
+ "maxItems": 20,
+ "type": "array"
+}Input schema / properties / replacement / properties / metadata / properties / actions / items / properties / data_modeAdded value: +{
+ "description": "demo or sample responses are not real data for the requested entity.",
+ "enum": [
+ "production",
+ "sandbox",
+ "demo",
+ "sample"
+ ],
+ "type": "string"
+}Input schema / properties / replacement / properties / metadata / properties / actions / items / properties / field_semanticsAdded value: +{
+ "additionalProperties": {
+ "maxLength": 300,
+ "type": "string"
+ },
+ "description": "Meaning of fields that differ across providers, e.g. which publication date.",
+ "type": "object"
+}Input schema / properties / replacement / properties / metadata / properties / actions / items / properties / identifiersAdded value: +{
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "argument": {
+ "maxLength": 100,
+ "minLength": 1,
+ "type": "string"
+ },
+ "location": {
+ "enum": [
+ "path",
+ "query",
+ "body",
+ "tool_argument"
+ ],
+ "type": "string"
+ },
+ "type": {
+ "enum": [
+ "doi",
+ "npm_package",
+ "repository",
+ "country_code",
+ "url",
+ "other"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "argument",
+ "location"
+ ],
+ "type": "object"
+ },
+ "maxItems": 10,
+ "type": "array"
+}Input schema / properties / replacement / properties / metadata / properties / actions / items / properties / lookup_modeAdded value: +{
+ "description": "exact_identifier returns the record for a supplied identifier; keyword_search ranks matches and may not contain it.",
+ "enum": [
+ "exact_identifier",
+ "keyword_search",
+ "filter_list",
+ "conversion",
+ "mutation"
+ ],
+ "type": "string"
+}Input schema / properties / replacement / properties / metadata / properties / actions / items / properties / output_coverageAdded value: +{
+ "additionalProperties": false,
+ "description": "Fields the documented response contains. Absent coverage is unknown, never complete.",
+ "properties": {
+ "fields": {
+ "items": {
+ "maxLength": 100,
+ "minLength": 1,
+ "type": "string"
+ },
+ "maxItems": 50,
+ "type": "array"
+ },
+ "omissions": {
+ "default": [],
+ "items": {
+ "maxLength": 100,
+ "minLength": 1,
+ "type": "string"
+ },
+ "maxItems": 50,
+ "type": "array"
+ },
+ "source_url": {
+ "$ref": "#/properties/replacement/properties/documentation_url"
+ }
+ },
+ "required": [
+ "fields"
+ ],
+ "type": "object"
+}Input schema / properties / replacement / properties / metadata / properties / actions / items / properties / subjectAdded value: +{
+ "description": "What the operation acts on, e.g. scholarly_work, repository, country, earthquake_event.",
+ "maxLength": 100,
+ "minLength": 2,
+ "type": "string"
+}Input schema / properties / replacement / properties / metadata / properties / actions / items / properties / validationAdded value: +{
+ "description": "Checks an agent applies to the response before treating it as task evidence.",
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "check": {
+ "maxLength": 300,
+ "minLength": 3,
+ "type": "string"
+ },
+ "field": {
+ "maxLength": 100,
+ "type": "string"
+ }
+ },
+ "required": [
+ "check"
+ ],
+ "type": "object"
+ },
+ "maxItems": 10,
+ "type": "array"
+}Input schema / properties / replacement / properties / metadata / properties / workflow / items / properties / prerequisites / items / enumPrevious value: -[
- "runtime",
- "credentials",
- "permissions",
- "billing",
- "spending"
-]New value: +[
+ "runtime",
+ "network",
+ "credentials",
+ "permissions",
+ "billing",
+ "entitlement",
+ "spending"
+]Input schema / properties / replacement / properties / metadata / properties / workflow / items / properties / prerequisites / maxItemsPrevious value: -5New value: +7Input schema / properties / replacement / properties / metadata / properties / workflow / items / properties / provides / items / enumPrevious value: -[
- "runtime",
- "credentials",
- "permissions",
- "billing",
- "spending"
-]New value: +[
+ "runtime",
+ "network",
+ "credentials",
+ "permissions",
+ "billing",
+ "entitlement",
+ "spending"
+]Input schema / properties / replacement / properties / metadata / properties / workflow / items / properties / provides / maxItemsPrevious value: -5New value: +7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Goes beyond annotations by stating specific authority requirements (publisher control, moderator), authentication needs (connected identity, community:comment scope), and return behavior (new revision and reassessment job). It also provides idempotency guidance ('Preserve request_id and payload on retries'), which aligns with the idempotentHint annotation and adds practical value. It could add more about what happens if the expected revision doesn't match.
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?
Four sentences with zero waste, front-loading the core action and then covering prerequisites, output, and retry guidance. Every sentence earns its place.
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?
The description covers the operation's purpose, authority requirements, return values, and retry semantics, which is good for a mutation tool. However, given the extreme complexity of the input schema (nested evidence, metadata, claims, etc.) and no output schema, the description is insufficient for an agent to understand how to construct the required payload without deep schema inspection.
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?
With 0% schema description coverage and 4 complex parameters (including a deeply nested `replacement` object), the description adds almost no parameter-level meaning. It mentions 'source-backed path correction' and 'expected revision' but doesn't explain the required `suggestion_id`, the structure of `replacement`, or the role of `request_id`. A user would need to inspect the raw schema to understand how to call this tool.
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+resource: 'Apply a reviewed source-backed path correction to an expected revision.' This clearly distinguishes the write/mutate nature of the tool from siblings like suggest_correction and resolve_correction. It lacks explicit differentiation from resolve_correction, which might also seem like it applies corrections.
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?
Provides clear context for use: 'Requires current publisher control or moderator authority.' It doesn't explicitly say when NOT to use it versus alternatives like suggest_correction, but the authority requirement gives a strong implicit usage gate.
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.