Submit a validated service declaration. Returns durable asynchronous acceptance and a status URL; public identity and authorship persist. Requires the connected identity and submission:write. Preserve request_id and payload on retries.
| Name | Required | Description | Default |
|---|---|---|---|
| request_id | Yes | ||
| submission | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / submission / properties / paths / items / 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 / submission / properties / paths / items / 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 / submission / properties / paths / items / 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 / submission / properties / paths / items / 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 / submission / properties / paths / items / 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 / submission / properties / paths / items / 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/submission/properties/entity/properties/operator/properties/source_url"
+ }
+ },
+ "required": [
+ "fields"
+ ],
+ "type": "object"
+}Input schema / properties / submission / properties / paths / items / 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 / submission / properties / paths / items / 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 / submission / properties / paths / items / 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 / submission / properties / paths / items / properties / metadata / properties / workflow / items / properties / prerequisites / maxItemsPrevious value: -5New value: +7Input schema / properties / submission / properties / paths / items / 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 / submission / properties / paths / items / properties / metadata / properties / workflow / items / properties / provides / maxItemsPrevious value: -5New value: +7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description adds genuinely new behavior: the return is a durable asynchronous acceptance with a status URL, public identity/authorship persist after submission, and the client must preserve request_id and payload across retries (consistent with idempotentHint rather than contradicting it). Failure modes and polling cadence remain unstated.
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 tight clauses with the purpose front-loaded and no filler; retry guidance is placed last where it belongs. 'Public identity and authorship persist' is the one slightly vague clause, but overall the density is high.
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?
For a mutation tool with no output schema, the description covers the return contract (async acceptance + status URL), authorization prerequisites, and retry semantics. It could go further by pointing at get_submission_status for polling the returned status URL or noting duplicate-submission behavior, but the essentials are present.
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?
Top-level schema description coverage is 0%, so the description must carry weight. It does explain the role of request_id as a retry-stable identity key (beyond the schema's mere minLength/maxLength), but it says nothing about the 'submission' object's shape or required contents, relying entirely on the deeply self-documenting nested schema.
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 and resource ('Submit a validated service declaration'), and the word 'validated' signals the required prior state. It does not, however, name the adjacent workflow siblings (draft_submission, validate_submission, preflight_submission, publish_declaration) that an agent must choose between.
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?
'Validated' implies a validate/preflight step must precede submission, and the required scope (submission:write) plus connected identity is stated as a precondition. There is no explicit when-not guidance or routing to alternatives such as draft_submission, so usage is only implied.
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.