transkribus_user_is_allowed_for_jobVerify if the current user is allowed to execute a specific job type using its implementation class name. Prevent unauthorized job runs by checking permissions before execution.
Check if the current user is allowed to run a specific job type.
| Name | Required | Description | Default |
|---|---|---|---|
| jobImpl | Yes | Job implementation class name |
Changes observed during successful MCP inspections.
v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds no additional behavioral details (e.g., that it returns a boolean, or requires specific authentication). It does not contradict annotations.
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?
The description is a single sentence, front-loading the purpose. It is efficient but could include more detail without being verbose. No waste.
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?
Given the simple nature (one parameter, read-only check), the description is minimally adequate. However, it lacks information about the return value (boolean) and the context of 'current user'. Without an output schema, the agent might benefit from knowing the result format.
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?
The input schema covers 100% of parameters with a basic description of jobImpl as 'Job implementation class name'. The description does not explain what values are valid or how to find the class name. Schema handles the parameter meaning, so baseline 3 is appropriate.
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?
The name and description clearly state the purpose: checking user permission for a job type. It is specific enough to distinguish from siblings like transkribus_auth_check_session which checks session validity, not job permission. However, it could be more explicit about the job type context.
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?
No guidance on when to use this tool versus alternatives such as transkribus_admin_authorize_users_for_job or transkribus_user_get_job_acl. The description provides no context for when a permission check is needed or what constitutes a 'job type'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.