Skip to main content
Glama
Sign In

Marziale Technologies

by tech.marziale.mcp
OverviewDiscussionsAdmin

Server Details

Send a request to Marziale Technologies, a New York FDSE firm. For business operators and talent.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over 21 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 5 tools

Disambiguation4/5

check_draft, get_offerings, and submit are clearly distinct actions. ask_with_picker and get_questions both concern the survey questions, but the 'Call this first, always' vs 'use this list only if elicitation:false' precedence rule makes the boundary explicit rather than confusing.

Naming Consistency4/5

Four tools follow a verb_noun pattern (ask_with_picker, check_draft, get_offerings, get_questions), all snake_case. The lone bare-verb 'submit' is a minor deviation but still readable and obviously a distinct action.

Tool Count5/5

Five tools is well-scoped for a survey/intake workflow: fetch info, ask, review, send, plus a fallback questions source. Each tool maps to a distinct step of the flow with no filler.

Completeness4/5

The lifecycle (read offerings -> elicit answers -> review -> submit, with fallback elicitation) is covered, including partial submissions and confirmation. Minor gaps: no status/result feedback after submit and no explicit re-edit mechanism beyond re-asking, but core flow is complete.

Available Tools

5 tools
ask_with_pickerAsk with pickersA
Read-only
Inspect

Call this first, always. It shows each question as a picker, one at a time, and returns the answers. Each picker has the option "Type my own answer". It sends nothing. If it returns paused: true, call it again with the picker_id it gave you, right away, until it returns completed or stopped. If it returns elicitation: false, ask the questions from get_questions in chat.

NameRequiredDescriptionDefault
picker_idNoLeave empty to start. To continue a paused picker, pass the picker_id from the last result.

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, which this description reinforces with the concrete claim 'It sends nothing'. Beyond that it discloses the full return protocol (paused/completed/stopped, elicitation:false, picker_id), which is significant since there is no output schema. It also describes the user-facing 'Type my own answer' behavior.

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?

Short, front-loaded with the imperative 'Call this first, always', and every sentence carries operational information (mechanism, no-send behavior, retry loop, fallback). No filler or repetition.

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?

With one optional parameter, no output schema, and only a readOnlyHint annotation, the description supplies exactly the missing pieces: the interactive mechanism, the return-state protocol, and the fallback path. An agent has everything needed to invoke and drive this tool 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 description coverage is 100% and the schema already documents picker_id, including that it is left empty to start and passed back to resume a paused picker. The description's retry guidance adds only marginal detail beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete action and mechanism: it shows each question as a picker, one at a time, and returns the answers. It also implicitly scopes the resource to the questions surfaced by get_questions, which separates it from siblings. The only weakness is that the 'resource' (the questions) is referenced rather than defined, so it leans slightly on sibling context.

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?

Explicit sequencing and alternatives: 'Call this first, always', a retry protocol when paused:true, and a fallback to asking questions from get_questions in chat when elicitation:false. It tells the agent both when to use it and what to do when it cannot be used.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

check_draftCheck a draftA
Read-only
Inspect

Check the draft. It returns a review to show the person. It sends nothing. Before submit, show the review from check_draft. It lists the answers in the person's words. It marks each missing required answer as 'Missing - required'. Ask the person to confirm it or correct it. Change answers until the person is done.

NameRequiredDescriptionDefault
nameNoQ1. Name, as the person gave it. Required.
needNoOptional. Both tracks. What the person needs or wants help with, in their own words, if they said it (for example in a follow-up or a typed answer). Do not ask an extra question for it.
townNoQ1. Town. Optional.
emailNoQ1. Email address where we can reply. Required.
trackNoWhat best describes you? client = "Operator: I make decisions inside of a business", talent = "Talent: I am talented and would like to talk". Required.
becomeNoOperator. Q6: What do you want it to become? One of: Stay as it is, but easier / Grow / Pass it on to someone / Not sure yet. Or the person's own typed words. Optional.
live_nowNoTalent. Q3: Where do you live now? One of: Lewis County / Elsewhere in the North Country / Elsewhere in New York / Outside New York. Or the person's own typed words. Optional.
draws_youNoTalent. Q5: What draws you to the North Country? One of: The work here / The place and the people / I want to move here / I want to work here remotely. Or the person's own typed words. Optional.
job_startNoOperator. Q3: How does a normal job start? One of: A customer calls or texts / They walk in / They order online / A repeat or contract customer / We go out and find them. Or the person's own typed words. Optional.
work_kindNoTalent. Q2: What kind of work do you do? One of: Software / Engineering or science / Trades / Design or media / Business or operations. Or the person's own typed words. Optional.
work_linkNoQ1, Talent only. Link to their work. Optional.
work_wantNoTalent. Q4: What kind of work do you want? One of: Full time / Part time / One project / Not sure yet. Or the person's own typed words. Optional.
build_nextNoTalent. Q6: What do you want to build in the next few years? One of: My own company / Deep skill in my craft / A part in running a local business / Not sure yet. Or the person's own typed words. Optional.
info_livesNoOperator. Q4: Where does most of your information live? One of: Paper / Spreadsheets / Software, for example QuickBooks / In people's heads / A mix. Or the person's own typed words. Optional.
become_moreNoOptional. The person's typed answer to your follow-up after Q: What do you want it to become?
why_startedNoOperator. Q5: Why did you start or take on this business? One of: I built it / Family business / I bought it / I saw a need in town. Or the person's own typed words. Optional.
anything_elseNoBoth tracks. Q7: Is there anything else you want us to know? Typed answer. Optional.
business_kindNoOperator. Q2: What kind of business is it? One of: Retail or food / Trades or construction / Farm or agriculture / Professional service / Manufacturing. Or the person's own typed words. Optional.
business_nameNoQ1, Operator only. Business name. Optional.
live_now_moreNoOptional. The person's typed answer to your follow-up after Q: Where do you live now?
draws_you_moreNoOptional. The person's typed answer to your follow-up after Q: What draws you to the North Country?
job_start_moreNoOptional. The person's typed answer to your follow-up after Q: How does a normal job start?
work_kind_moreNoOptional. The person's typed answer to your follow-up after Q: What kind of work do you do?
work_want_moreNoOptional. The person's typed answer to your follow-up after Q: What kind of work do you want?
build_next_moreNoOptional. The person's typed answer to your follow-up after Q: What do you want to build in the next few years?
info_lives_moreNoOptional. The person's typed answer to your follow-up after Q: Where does most of your information live?
why_started_moreNoOptional. The person's typed answer to your follow-up after Q: Why did you start or take on this business?
anything_else_moreNoOptional. The person's typed answer to your follow-up after Q: Is there anything else you want us to know?
business_kind_moreNoOptional. The person's typed answer to your follow-up after Q: What kind of business is it?

TDQS

A3.9/5.0
Behavior4/5

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

With readOnlyHint=true already covering safety, the description adds concrete behavioral detail: 'It sends nothing' (consistent with the annotation), it returns a review to show the person, and it marks missing required answers as 'Missing - required'. It does not clarify persistence or whether the review is stored, but the added context is well beyond the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short, front-loaded sentences that each add a distinct fact: output, non-sending, sequencing, formatting, and the confirm/correct loop. The only waste is the opening phrase duplicating the title, and the staccato fragments are slightly choppy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain the return value, and it does ('returns a review... lists the answers... marks each missing required'). For a large 29-parameter validation tool the schema covers inputs fully, leaving only minor gaps like whether the review persists.

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 100% across all 29 parameters, so the schema already carries the semantics (question numbers, tracks, required flags). The description adds only that required answers appear as 'Missing - required', which is marginal beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence 'Check the draft' largely restates the title, but the following sentences specify the real output: a review listing answers in the person's words with missing required answers flagged. This distinguishes it from the sibling 'submit' by making clear it produces a review rather than sending anything.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit sequencing guidance: 'Before submit, show the review from check_draft,' which ties it to the sibling submit tool, plus an implied loop ('Change answers until the person is done'). No explicit when-not-to-use, but the when-to-use is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_offeringsWhat Marziale Technologies doesC
Read-only
Inspect

Read what we do and the next steps. Read-only.

NameRequiredDescriptionDefault

No parameters

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, and the description merely echoes this with "Read-only," adding no context beyond the structured data. It does not describe the kind of content returned, its size, or any constraints, which matters since there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, and the read-only note is front-loaded at the end as a quick signal. It is efficient, though arguably too sparse to be fully informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple zero-parameter tool this is minimally adequate, but with no output schema the description should say more about what "what we do and the next steps" actually returns. As written, an agent knows the operation is a read but not what content to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to clarify. Schema description coverage is 100% for the empty object, leaving no gap to compensate for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description largely restates the title ("What Marziale Technologies does") with "Read what we do," so it functions as tautology rather than a specific verb+resource statement. "and the next steps" is vague about what content is actually returned, and nothing distinguishes it from siblings like get_questions or check_draft.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance and no mention of alternatives among ask_with_picker, check_draft, get_questions, or submit. The only hint is that it is a read operation, which the annotations already imply.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_questionsQuestions and rulesA
Read-only
Inspect

Get the questions, choices, and rules. Read-only. Call ask_with_picker first. Use this list only if ask_with_picker returns elicitation: false. First ask "What best describes you?". Then say that track's opening and the how-to-answer line. Then ask that track's questions 1 to 7 in order. Question 1 asks for name and email. Ask one question at a time. Show the options word for word as a list. End each list with "Or type your own answer." If the person types their own answer, keep their words. Questions 1 and 7 and every follow-up have a typed answer only. The person can skip any question.

First, for all: What best describes you?

  1. Operator: I make decisions inside of a business

  2. Talent: I am talented and would like to talk

Operator (track: client): OPENING (say this first) This conversation is for Marziale Technologies. Your answers go only to Marziale Technologies, and a person there reads every message. Your answers help us understand your business and follow up with you. Please do not share anything you need kept confidential until we have an agreement. You can skip any question.

HOW TO ANSWER (show this once, after the opening) Pick one of the options, or type your own answer. Both are fine.

QUESTIONS (show the options as a list, and end each list with "Or type your own answer.")

  1. Your name, your business name, your town, and an email address where we can reply. (Typed answer only.)

  2. What kind of business is it? A) Retail or food B) Trades or construction C) Farm or agriculture D) Professional service E) Manufacturing Or type your own answer.

  3. How does a normal job start? A) A customer calls or texts B) They walk in C) They order online D) A repeat or contract customer E) We go out and find them Or type your own answer.

  4. Where does most of your information live? A) Paper B) Spreadsheets C) Software, for example QuickBooks D) In people's heads E) A mix Or type your own answer.

  5. Why did you start or take on this business? A) I built it B) Family business C) I bought it D) I saw a need in town Or type your own answer.

  6. What do you want it to become? A) Stay as it is, but easier B) Grow C) Pass it on to someone D) Not sure yet Or type your own answer.

  7. Is there anything else you want us to know? (Typed answer only. They can skip it.)

RULES FOR THE ASSISTANT

  • Ask one question at a time.

  • After each answer, ask one short follow-up in their words. A follow-up has a typed answer only.

  • Never push them toward a problem to fix.

  • Do not explain our methods or goals beyond "we want to understand your business."

  • Say plainly that you are an AI assistant if they ask, or if they seem to think you are a person.

  • If they stop early, ask one time for an email address, and ask if we may send what they shared so far.

  • At the end, show a short summary in their words. Ask them to confirm it or correct it, then send it.

Talent (track: talent): OPENING (say this first) This conversation is for Marziale Technologies. Your answers go only to Marziale Technologies, and a person there reads every message. Your answers help us understand you and follow up with you. Please do not share anything you need kept confidential. You can skip any question.

HOW TO ANSWER (show this once, after the opening) Pick one of the options, or type your own answer. Both are fine.

QUESTIONS (show the options as a list, and end each list with "Or type your own answer.")

  1. Your name, your town, an email address where we can reply, and a link to your work if you have one. (Typed answer only.)

  2. What kind of work do you do? A) Software B) Engineering or science C) Trades D) Design or media E) Business or operations Or type your own answer.

  3. Where do you live now? A) Lewis County B) Elsewhere in the North Country C) Elsewhere in New York D) Outside New York Or type your own answer.

  4. What kind of work do you want? A) Full time B) Part time C) One project D) Not sure yet Or type your own answer.

  5. What draws you to the North Country? A) The work here B) The place and the people C) I want to move here D) I want to work here remotely Or type your own answer.

  6. What do you want to build in the next few years? A) My own company B) Deep skill in my craft C) A part in running a local business D) Not sure yet Or type your own answer.

  7. Is there anything else you want us to know? (Typed answer only. They can skip it.)

RULES FOR THE ASSISTANT

  • Ask one question at a time.

  • After each answer, ask one short follow-up in their words. A follow-up has a typed answer only.

  • Do not promise a job, pay, or a start date.

  • Do not explain our methods or goals beyond "we want to understand you and your work."

  • Say plainly that you are an AI assistant if they ask, or if they seem to think you are a person.

  • Never ask about age, family, health, religion, national origin, or pay history. If they bring it up, do not follow up on it.

  • If they stop early, ask one time for an email address, and ask if we may send what they shared so far.

  • At the end, show a short summary in their words. Ask them to confirm it or correct it, then send it.

Typed answers: max 1200 characters each.

NameRequiredDescriptionDefault

No parameters

TDQS

A3.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint true, and the description merely repeats 'Read-only.' Beyond that it provides conversational scripts and assistant rules, not tool-level behavioral traits such as auth needs, rate limits, error behavior, or output format. With annotations covering the safety profile, this adds little beyond the structured annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It front-loads the core usage correctly, but then embeds thousands of characters of questionnaire content and assistant rules, making it grossly oversized for a tool definition. It is structured but fails conciseness; this payload belongs in the tool's return value, not in its description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must convey what the tool returns; it does provide the full questions, choices, and rules. However, it never states the return format or how that data is organized, leaving a small gap in output framing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and schema description coverage is 100%, so the baseline is 4. The description does not need to explain parameters, and its note about typed answers being max 1200 characters concerns interactive content, not tool parameters.

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 the specific verb 'Get' and resources 'questions, choices, and rules', and distinguishes itself from the sibling ask_with_picker by saying to use this list only if ask_with_picker returns elicitation: false. An agent can identify it as the fallback content source without opening another schema.

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 to call ask_with_picker first and use this list only when ask_with_picker returns elicitation: false, then supplies detailed sequencing rules. This is as explicit as it gets for when to use this tool versus its alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

submitSend the request (needs a yes)AInspect

Send the request to Marziale Technologies. Use only after the person saw the review, the legal line, the privacy line and link, and said yes. Required: track, name, email, review_shown, legal_and_privacy_shown, person_said_yes. A partial request is fine. It needs the track, a name, and an email. Send it only after the person says yes.

NameRequiredDescriptionDefault
nameYesQ1. Name, as the person gave it. Required.
needNoOptional. Both tracks. What the person needs or wants help with, in their own words, if they said it (for example in a follow-up or a typed answer). Do not ask an extra question for it.
townNoQ1. Town. Optional.
emailYesQ1. Email address where we can reply. Required.
trackYesWhat best describes you? client = "Operator: I make decisions inside of a business", talent = "Talent: I am talented and would like to talk". Required.
becomeNoOperator. Q6: What do you want it to become? One of: Stay as it is, but easier / Grow / Pass it on to someone / Not sure yet. Or the person's own typed words. Optional.
live_nowNoTalent. Q3: Where do you live now? One of: Lewis County / Elsewhere in the North Country / Elsewhere in New York / Outside New York. Or the person's own typed words. Optional.
draws_youNoTalent. Q5: What draws you to the North Country? One of: The work here / The place and the people / I want to move here / I want to work here remotely. Or the person's own typed words. Optional.
job_startNoOperator. Q3: How does a normal job start? One of: A customer calls or texts / They walk in / They order online / A repeat or contract customer / We go out and find them. Or the person's own typed words. Optional.
work_kindNoTalent. Q2: What kind of work do you do? One of: Software / Engineering or science / Trades / Design or media / Business or operations. Or the person's own typed words. Optional.
work_linkNoQ1, Talent only. Link to their work. Optional.
work_wantNoTalent. Q4: What kind of work do you want? One of: Full time / Part time / One project / Not sure yet. Or the person's own typed words. Optional.
build_nextNoTalent. Q6: What do you want to build in the next few years? One of: My own company / Deep skill in my craft / A part in running a local business / Not sure yet. Or the person's own typed words. Optional.
client_appNoOptional. Name of your app.
info_livesNoOperator. Q4: Where does most of your information live? One of: Paper / Spreadsheets / Software, for example QuickBooks / In people's heads / A mix. Or the person's own typed words. Optional.
become_moreNoOptional. The person's typed answer to your follow-up after Q: What do you want it to become?
why_startedNoOperator. Q5: Why did you start or take on this business? One of: I built it / Family business / I bought it / I saw a need in town. Or the person's own typed words. Optional.
review_shownYesTrue only if you showed the review from check_draft and asked if the person wants to change any answer.
anything_elseNoBoth tracks. Q7: Is there anything else you want us to know? Typed answer. Optional.
business_kindNoOperator. Q2: What kind of business is it? One of: Retail or food / Trades or construction / Farm or agriculture / Professional service / Manufacturing. Or the person's own typed words. Optional.
business_nameNoQ1, Operator only. Business name. Optional.
live_now_moreNoOptional. The person's typed answer to your follow-up after Q: Where do you live now?
draws_you_moreNoOptional. The person's typed answer to your follow-up after Q: What draws you to the North Country?
job_start_moreNoOptional. The person's typed answer to your follow-up after Q: How does a normal job start?
work_kind_moreNoOptional. The person's typed answer to your follow-up after Q: What kind of work do you do?
work_want_moreNoOptional. The person's typed answer to your follow-up after Q: What kind of work do you want?
build_next_moreNoOptional. The person's typed answer to your follow-up after Q: What do you want to build in the next few years?
info_lives_moreNoOptional. The person's typed answer to your follow-up after Q: Where does most of your information live?
person_said_yesYesTrue only if the person said yes to send this draft.
why_started_moreNoOptional. The person's typed answer to your follow-up after Q: Why did you start or take on this business?
anything_else_moreNoOptional. The person's typed answer to your follow-up after Q: Is there anything else you want us to know?
business_kind_moreNoOptional. The person's typed answer to your follow-up after Q: What kind of business is it?
legal_and_privacy_shownYesTrue only if you showed the legal line, the privacy line, and the privacy link.

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare openWorldHint=true, idempotentHint=false, readOnlyHint=false, so the safety profile is already available. The description adds genuinely non-annotation behavior: submission is gated on explicit human consent flags and a partial request is acceptable. It stops short of saying whether a repeat call resends or duplicates (relevant given idempotentHint=false).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short overall and the consent gate is front-loaded, but the requirement list and 'send only after the person says yes' are repeated almost verbatim, which wastes space without adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 33-parameter submission tool with no output schema, the description covers the required inputs and the consent precondition, but says nothing about the outcome on success, error handling, or resend/duplicate behavior despite non-idempotent annotations.

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 100% across 33 parameters, so the schema carries the semantics. The description restates the six required fields and notes partial requests are fine, but adds no syntax, format, or track-specific meaning beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Send the request to Marziale Technologies'), and the gating language makes clear this is the final submission step rather than a drafting step like check_draft. It does not explicitly name the sibling it follows on from, but the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition: only after the person saw the review, the legal line, the privacy line and link, and said yes. This is clear when-to-use guidance. It does not name alternatives (e.g. check_draft) or state when NOT to use it beyond the consent gate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updates
    • Changedask_with_picker1 field changed
      • addedInput schema / properties / picker_id
        Added value: +{
+  "description": "Leave empty to start. To continue a paused picker, pass the picker_id from the last result.",
+  "maxLength": 64,
+  "type": "string"
+}
    • Changedcheck_draft17 fields changed
      • changedInput schema / properties / anything_else / description
        Previous value: -"Talent. Q6: Is there anything else you want us to know? Typed answer. Optional."New value: +"Both tracks. Q7: Is there anything else you want us to know? Typed answer. Optional."
      • changedInput schema / properties / become / description
        Previous value: -"Operator. Q5: What do you want it to become? One of: Stay as it is, but easier / Grow / Pass it on to someone / Not sure yet. Or the person's own typed words. Optional."New value: +"Operator. Q6: What do you want it to become? One of: Stay as it is, but easier / Grow / Pass it on to someone / Not sure yet. Or the person's own typed words. Optional."
      • changedInput schema / properties / build_next / description
        Previous value: -"Talent. Q5: What do you want to build in the next few years? One of: My own company / Deep skill in my craft / A part in running a local business / Not sure yet. Or the person's own typed words. Optional."New value: +"Talent. Q6: What do you want to build in the next few years? One of: My own company / Deep skill in my craft / A part in running a local business / Not sure yet. Or the person's own typed words. Optional."
      • changedInput schema / properties / business_kind / description
        Previous value: -"Operator. Q1: What kind of business is it? One of: Retail or food / Trades or construction / Farm or agriculture / Professional service / Manufacturing. Or the person's own typed words. Optional."New value: +"Operator. Q2: What kind of business is it? One of: Retail or food / Trades or construction / Farm or agriculture / Professional service / Manufacturing. Or the person's own typed words. Optional."
      • changedInput schema / properties / business_name / description
        Previous value: -"Q7, Operator only. Business name. Optional."New value: +"Q1, Operator only. Business name. Optional."
      • changedInput schema / properties / draws_you / description
        Previous value: -"Talent. Q4: What draws you to the North Country? One of: The work here / The place and the people / I want to move here / I want to work here remotely. Or the person's own typed words. Optional."New value: +"Talent. Q5: What draws you to the North Country? One of: The work here / The place and the people / I want to move here / I want to work here remotely. Or the person's own typed words. Optional."
      • changedInput schema / properties / email / description
        Previous value: -"Q7. Email address where we can reply. Required."New value: +"Q1. Email address where we can reply. Required."
      • changedInput schema / properties / info_lives / description
        Previous value: -"Operator. Q3: Where does most of your information live? One of: Paper / Spreadsheets / Software, for example QuickBooks / In people's heads / A mix. Or the person's own typed words. Optional."New value: +"Operator. Q4: Where does most of your information live? One of: Paper / Spreadsheets / Software, for example QuickBooks / In people's heads / A mix. Or the person's own typed words. Optional."
      • changedInput schema / properties / job_start / description
        Previous value: -"Operator. Q2: How does a normal job start? One of: A customer calls or texts / They walk in / They order online / A repeat or contract customer / We go out and find them. Or the person's own typed words. Optional."New value: +"Operator. Q3: How does a normal job start? One of: A customer calls or texts / They walk in / They order online / A repeat or contract customer / We go out and find them. Or the person's own typed words. Optional."
      • changedInput schema / properties / live_now / description
        Previous value: -"Talent. Q2: Where do you live now? One of: Lewis County / Elsewhere in the North Country / Elsewhere in New York / Outside New York. Or the person's own typed words. Optional."New value: +"Talent. Q3: Where do you live now? One of: Lewis County / Elsewhere in the North Country / Elsewhere in New York / Outside New York. Or the person's own typed words. Optional."
      • changedInput schema / properties / name / description
        Previous value: -"Q7. Name, as the person gave it. Required."New value: +"Q1. Name, as the person gave it. Required."
      • addedInput schema / properties / need
        Added value: +{
+  "description": "Optional. Both tracks. What the person needs or wants help with, in their own words, if they said it (for example in a follow-up or a typed answer). Do not ask an extra question for it.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • changedInput schema / properties / town / description
        Previous value: -"Q7. Town. Optional."New value: +"Q1. Town. Optional."
      • changedInput schema / properties / why_started / description
        Previous value: -"Operator. Q4: Why did you start or take on this business? One of: I built it / Family business / I bought it / I saw a need in town. Or the person's own typed words. Optional."New value: +"Operator. Q5: Why did you start or take on this business? One of: I built it / Family business / I bought it / I saw a need in town. Or the person's own typed words. Optional."
      • changedInput schema / properties / work_kind / description
        Previous value: -"Talent. Q1: What kind of work do you do? One of: Software / Engineering or science / Trades / Design or media / Business or operations. Or the person's own typed words. Optional."New value: +"Talent. Q2: What kind of work do you do? One of: Software / Engineering or science / Trades / Design or media / Business or operations. Or the person's own typed words. Optional."
      • changedInput schema / properties / work_link / description
        Previous value: -"Q7, Talent only. Link to their work. Optional."New value: +"Q1, Talent only. Link to their work. Optional."
      • changedInput schema / properties / work_want / description
        Previous value: -"Talent. Q3: What kind of work do you want? One of: Full time / Part time / One project / Not sure yet. Or the person's own typed words. Optional."New value: +"Talent. Q4: What kind of work do you want? One of: Full time / Part time / One project / Not sure yet. Or the person's own typed words. Optional."
    • Changedsubmit17 fields changed
      • changedInput schema / properties / anything_else / description
        Previous value: -"Talent. Q6: Is there anything else you want us to know? Typed answer. Optional."New value: +"Both tracks. Q7: Is there anything else you want us to know? Typed answer. Optional."
      • changedInput schema / properties / become / description
        Previous value: -"Operator. Q5: What do you want it to become? One of: Stay as it is, but easier / Grow / Pass it on to someone / Not sure yet. Or the person's own typed words. Optional."New value: +"Operator. Q6: What do you want it to become? One of: Stay as it is, but easier / Grow / Pass it on to someone / Not sure yet. Or the person's own typed words. Optional."
      • changedInput schema / properties / build_next / description
        Previous value: -"Talent. Q5: What do you want to build in the next few years? One of: My own company / Deep skill in my craft / A part in running a local business / Not sure yet. Or the person's own typed words. Optional."New value: +"Talent. Q6: What do you want to build in the next few years? One of: My own company / Deep skill in my craft / A part in running a local business / Not sure yet. Or the person's own typed words. Optional."
      • changedInput schema / properties / business_kind / description
        Previous value: -"Operator. Q1: What kind of business is it? One of: Retail or food / Trades or construction / Farm or agriculture / Professional service / Manufacturing. Or the person's own typed words. Optional."New value: +"Operator. Q2: What kind of business is it? One of: Retail or food / Trades or construction / Farm or agriculture / Professional service / Manufacturing. Or the person's own typed words. Optional."
      • changedInput schema / properties / business_name / description
        Previous value: -"Q7, Operator only. Business name. Optional."New value: +"Q1, Operator only. Business name. Optional."
      • changedInput schema / properties / draws_you / description
        Previous value: -"Talent. Q4: What draws you to the North Country? One of: The work here / The place and the people / I want to move here / I want to work here remotely. Or the person's own typed words. Optional."New value: +"Talent. Q5: What draws you to the North Country? One of: The work here / The place and the people / I want to move here / I want to work here remotely. Or the person's own typed words. Optional."
      • changedInput schema / properties / email / description
        Previous value: -"Q7. Email address where we can reply. Required."New value: +"Q1. Email address where we can reply. Required."
      • changedInput schema / properties / info_lives / description
        Previous value: -"Operator. Q3: Where does most of your information live? One of: Paper / Spreadsheets / Software, for example QuickBooks / In people's heads / A mix. Or the person's own typed words. Optional."New value: +"Operator. Q4: Where does most of your information live? One of: Paper / Spreadsheets / Software, for example QuickBooks / In people's heads / A mix. Or the person's own typed words. Optional."
      • changedInput schema / properties / job_start / description
        Previous value: -"Operator. Q2: How does a normal job start? One of: A customer calls or texts / They walk in / They order online / A repeat or contract customer / We go out and find them. Or the person's own typed words. Optional."New value: +"Operator. Q3: How does a normal job start? One of: A customer calls or texts / They walk in / They order online / A repeat or contract customer / We go out and find them. Or the person's own typed words. Optional."
      • changedInput schema / properties / live_now / description
        Previous value: -"Talent. Q2: Where do you live now? One of: Lewis County / Elsewhere in the North Country / Elsewhere in New York / Outside New York. Or the person's own typed words. Optional."New value: +"Talent. Q3: Where do you live now? One of: Lewis County / Elsewhere in the North Country / Elsewhere in New York / Outside New York. Or the person's own typed words. Optional."
      • changedInput schema / properties / name / description
        Previous value: -"Q7. Name, as the person gave it. Required."New value: +"Q1. Name, as the person gave it. Required."
      • addedInput schema / properties / need
        Added value: +{
+  "description": "Optional. Both tracks. What the person needs or wants help with, in their own words, if they said it (for example in a follow-up or a typed answer). Do not ask an extra question for it.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • changedInput schema / properties / town / description
        Previous value: -"Q7. Town. Optional."New value: +"Q1. Town. Optional."
      • changedInput schema / properties / why_started / description
        Previous value: -"Operator. Q4: Why did you start or take on this business? One of: I built it / Family business / I bought it / I saw a need in town. Or the person's own typed words. Optional."New value: +"Operator. Q5: Why did you start or take on this business? One of: I built it / Family business / I bought it / I saw a need in town. Or the person's own typed words. Optional."
      • changedInput schema / properties / work_kind / description
        Previous value: -"Talent. Q1: What kind of work do you do? One of: Software / Engineering or science / Trades / Design or media / Business or operations. Or the person's own typed words. Optional."New value: +"Talent. Q2: What kind of work do you do? One of: Software / Engineering or science / Trades / Design or media / Business or operations. Or the person's own typed words. Optional."
      • changedInput schema / properties / work_link / description
        Previous value: -"Q7, Talent only. Link to their work. Optional."New value: +"Q1, Talent only. Link to their work. Optional."
      • changedInput schema / properties / work_want / description
        Previous value: -"Talent. Q3: What kind of work do you want? One of: Full time / Part time / One project / Not sure yet. Or the person's own typed words. Optional."New value: +"Talent. Q4: What kind of work do you want? One of: Full time / Part time / One project / Not sure yet. Or the person's own typed words. Optional."
  2. 2 tool updates
    • Changedcheck_draft49 fields changed
      • removedInput schema / properties / achievements
        Removed value: -{
-  "description": "List of entries. Keys: achievement, year.",
-  "items": {
-    "additionalProperties": {
-      "maxLength": 4000,
-      "type": "string"
-    },
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  "maxItems": 20,
-  "type": "array"
-}
      • changedInput schema / properties / anything_else / description
        Previous value: -"Both. Optional. Anything else we should know? Max 1200 characters."New value: +"Talent. Q6: Is there anything else you want us to know? Typed answer. Optional."
      • changedInput schema / properties / anything_else / maxLength
        Previous value: -5000New value: +1200
      • addedInput schema / properties / anything_else_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: Is there anything else you want us to know?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / become
        Added value: +{
+  "description": "Operator. Q5: What do you want it to become? One of: Stay as it is, but easier / Grow / Pass it on to someone / Not sure yet. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / become_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: What do you want it to become?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / build_next
        Added value: +{
+  "description": "Talent. Q5: What do you want to build in the next few years? One of: My own company / Deep skill in my craft / A part in running a local business / Not sure yet. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / build_next_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: What do you want to build in the next few years?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / business_kind
        Added value: +{
+  "description": "Operator. Q1: What kind of business is it? One of: Retail or food / Trades or construction / Farm or agriculture / Professional service / Manufacturing. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / business_kind_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: What kind of business is it?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • changedInput schema / properties / business_name / description
        Previous value: -"Client. Optional."New value: +"Q7, Operator only. Business name. Optional."
      • removedInput schema / properties / business_type
        Removed value: -{
-  "description": "Client. One of: Retail or shop / Restaurant or food / Farm, dairy, or food plant / Trades or construction / Health or professional office / Nonprofit or public agency / Other.",
-  "maxLength": 100,
-  "type": "string"
-}
      • removedInput schema / properties / business_type_other
        Removed value: -{
-  "description": "Client. Required if business_type is Other.",
-  "maxLength": 300,
-  "type": "string"
-}
      • addedInput schema / properties / draws_you
        Added value: +{
+  "description": "Talent. Q4: What draws you to the North Country? One of: The work here / The place and the people / I want to move here / I want to work here remotely. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / draws_you_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: What draws you to the North Country?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • removedInput schema / properties / education
        Removed value: -{
-  "description": "List of entries. Keys: school, degree, field, grad_year, test_scores (optional).",
-  "items": {
-    "additionalProperties": {
-      "maxLength": 4000,
-      "type": "string"
-    },
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  "maxItems": 20,
-  "type": "array"
-}
      • changedInput schema / properties / email / description
        Previous value: -"Email for the reply. Required."New value: +"Q7. Email address where we can reply. Required."
      • removedInput schema / properties / experience
        Removed value: -{
-  "description": "List of entries. Keys: title, company, start, end, what_you_did.",
-  "items": {
-    "additionalProperties": {
-      "maxLength": 4000,
-      "type": "string"
-    },
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  "maxItems": 20,
-  "type": "array"
-}
      • removedInput schema / properties / hours
        Removed value: -{
-  "description": "Client. One of: Under 2 / 2 to 5 / 5 to 10 / 10 to 20 / Over 20.",
-  "maxLength": 50,
-  "type": "string"
-}
      • removedInput schema / properties / hours_exact
        Removed value: -{
-  "description": "Client. Optional. About how many hours.",
-  "maxLength": 100,
-  "type": "string"
-}
      • addedInput schema / properties / info_lives
        Added value: +{
+  "description": "Operator. Q3: Where does most of your information live? One of: Paper / Spreadsheets / Software, for example QuickBooks / In people's heads / A mix. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / info_lives_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: Where does most of your information live?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / job_start
        Added value: +{
+  "description": "Operator. Q2: How does a normal job start? One of: A customer calls or texts / They walk in / They order online / A repeat or contract customer / We go out and find them. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / job_start_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: How does a normal job start?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • removedInput schema / properties / links
        Removed value: -{
-  "additionalProperties": {
-    "maxLength": 2000,
-    "type": "string"
-  },
-  "description": "Talent. Keys: linkedin, github, website, other_links.",
-  "propertyNames": {
-    "type": "string"
-  },
-  "type": "object"
-}
      • addedInput schema / properties / live_now
        Added value: +{
+  "description": "Talent. Q2: Where do you live now? One of: Lewis County / Elsewhere in the North Country / Elsewhere in New York / Outside New York. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / live_now_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: Where do you live now?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • changedInput schema / properties / name / description
        Previous value: -"Name, as the person gave it. Required."New value: +"Q7. Name, as the person gave it. Required."
      • removedInput schema / properties / origin
        Removed value: -{
-  "description": "Both. Client: When did this problem start costing you time? Talent: When did you start building on your own, and why? Max 1200 characters.",
-  "maxLength": 5000,
-  "type": "string"
-}
      • removedInput schema / properties / projects
        Removed value: -{
-  "description": "List of entries. Keys: name, link, what_it_is.",
-  "items": {
-    "additionalProperties": {
-      "maxLength": 4000,
-      "type": "string"
-    },
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  "maxItems": 20,
-  "type": "array"
-}
      • removedInput schema / properties / publications
        Removed value: -{
-  "description": "List of entries. Keys: title, venue, year, link.",
-  "items": {
-    "additionalProperties": {
-      "maxLength": 4000,
-      "type": "string"
-    },
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  "maxItems": 20,
-  "type": "array"
-}
      • removedInput schema / properties / result_90_days
        Removed value: -{
-  "description": "Client. A good result in 90 days. The owner's words.",
-  "maxLength": 4000,
-  "type": "string"
-}
      • removedInput schema / properties / resume_link
        Removed value: -{
-  "description": "Talent. Optional resume link.",
-  "maxLength": 500,
-  "type": "string"
-}
      • removedInput schema / properties / status
        Removed value: -{
-  "description": "Both. Where are you right now? Client: We do it by hand / We use a tool that falls short / We tried a fix that did not work / Not sure where to start. Talent: In school / Working full-time / Working part-time / Building my own thing / Between things.",
-  "maxLength": 100,
-  "type": "string"
-}
      • removedInput schema / properties / story
        Removed value: -{
-  "description": "Talent. Required. Most impressive thing built or done. Max 1200 characters.",
-  "maxLength": 5000,
-  "type": "string"
-}
      • removedInput schema / properties / story_link
        Removed value: -{
-  "description": "Talent. Optional link for the story.",
-  "maxLength": 500,
-  "type": "string"
-}
      • removedInput schema / properties / task
        Removed value: -{
-  "description": "Client. One of: Scheduling and bookings / Orders and inventory / Billing and payments / Customer calls, texts, and email / Reports and paperwork / Other.",
-  "maxLength": 100,
-  "type": "string"
-}
      • removedInput schema / properties / task_other
        Removed value: -{
-  "description": "Client. Required if task is Other.",
-  "maxLength": 2000,
-  "type": "string"
-}
      • changedInput schema / properties / town / description
        Previous value: -"Client. Town of the business."New value: +"Q7. Town. Optional."
      • changedInput schema / properties / track / description
        Previous value: -"client or talent. Required."New value: +"What best describes you? client = \"Operator: I make decisions inside of a business\", talent = \"Talent: I am talented and would like to talk\". Required."
      • removedInput schema / properties / when
        Removed value: -{
-  "description": "Both. Client: When do you want this fixed? As soon as possible / Within 3 months / 3 to 6 months / 6 to 12 months / Just looking. Talent: When could you start? Already full-time / Within 3 months / 3 to 6 months / 6 to 12 months / Still exploring.",
-  "maxLength": 100,
-  "type": "string"
-}
      • removedInput schema / properties / who
        Removed value: -{
-  "description": "Client. One of: The owner / One staff member / Several staff / An outside service.",
-  "maxLength": 100,
-  "type": "string"
-}
      • addedInput schema / properties / why_started
        Added value: +{
+  "description": "Operator. Q4: Why did you start or take on this business? One of: I built it / Family business / I bought it / I saw a need in town. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / why_started_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: Why did you start or take on this business?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / work_kind
        Added value: +{
+  "description": "Talent. Q1: What kind of work do you do? One of: Software / Engineering or science / Trades / Design or media / Business or operations. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / work_kind_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: What kind of work do you do?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / work_link
        Added value: +{
+  "description": "Q7, Talent only. Link to their work. Optional.",
+  "maxLength": 500,
+  "type": "string"
+}
      • addedInput schema / properties / work_want
        Added value: +{
+  "description": "Talent. Q3: What kind of work do you want? One of: Full time / Part time / One project / Not sure yet. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / work_want_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: What kind of work do you want?",
+  "maxLength": 1200,
+  "type": "string"
+}
    • Changedsubmit50 fields changed
      • removedInput schema / properties / achievements
        Removed value: -{
-  "description": "List of entries. Keys: achievement, year.",
-  "items": {
-    "additionalProperties": {
-      "maxLength": 4000,
-      "type": "string"
-    },
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  "maxItems": 20,
-  "type": "array"
-}
      • changedInput schema / properties / anything_else / description
        Previous value: -"Both. Optional. Anything else we should know? Max 1200 characters."New value: +"Talent. Q6: Is there anything else you want us to know? Typed answer. Optional."
      • changedInput schema / properties / anything_else / maxLength
        Previous value: -5000New value: +1200
      • addedInput schema / properties / anything_else_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: Is there anything else you want us to know?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / become
        Added value: +{
+  "description": "Operator. Q5: What do you want it to become? One of: Stay as it is, but easier / Grow / Pass it on to someone / Not sure yet. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / become_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: What do you want it to become?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / build_next
        Added value: +{
+  "description": "Talent. Q5: What do you want to build in the next few years? One of: My own company / Deep skill in my craft / A part in running a local business / Not sure yet. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / build_next_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: What do you want to build in the next few years?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / business_kind
        Added value: +{
+  "description": "Operator. Q1: What kind of business is it? One of: Retail or food / Trades or construction / Farm or agriculture / Professional service / Manufacturing. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / business_kind_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: What kind of business is it?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • changedInput schema / properties / business_name / description
        Previous value: -"Client. Optional."New value: +"Q7, Operator only. Business name. Optional."
      • removedInput schema / properties / business_type
        Removed value: -{
-  "description": "Client. One of: Retail or shop / Restaurant or food / Farm, dairy, or food plant / Trades or construction / Health or professional office / Nonprofit or public agency / Other.",
-  "maxLength": 100,
-  "type": "string"
-}
      • removedInput schema / properties / business_type_other
        Removed value: -{
-  "description": "Client. Required if business_type is Other.",
-  "maxLength": 300,
-  "type": "string"
-}
      • addedInput schema / properties / draws_you
        Added value: +{
+  "description": "Talent. Q4: What draws you to the North Country? One of: The work here / The place and the people / I want to move here / I want to work here remotely. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / draws_you_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: What draws you to the North Country?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • removedInput schema / properties / education
        Removed value: -{
-  "description": "List of entries. Keys: school, degree, field, grad_year, test_scores (optional).",
-  "items": {
-    "additionalProperties": {
-      "maxLength": 4000,
-      "type": "string"
-    },
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  "maxItems": 20,
-  "type": "array"
-}
      • changedInput schema / properties / email / description
        Previous value: -"Email for the reply. Required."New value: +"Q7. Email address where we can reply. Required."
      • removedInput schema / properties / experience
        Removed value: -{
-  "description": "List of entries. Keys: title, company, start, end, what_you_did.",
-  "items": {
-    "additionalProperties": {
-      "maxLength": 4000,
-      "type": "string"
-    },
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  "maxItems": 20,
-  "type": "array"
-}
      • removedInput schema / properties / hours
        Removed value: -{
-  "description": "Client. One of: Under 2 / 2 to 5 / 5 to 10 / 10 to 20 / Over 20.",
-  "maxLength": 50,
-  "type": "string"
-}
      • removedInput schema / properties / hours_exact
        Removed value: -{
-  "description": "Client. Optional. About how many hours.",
-  "maxLength": 100,
-  "type": "string"
-}
      • addedInput schema / properties / info_lives
        Added value: +{
+  "description": "Operator. Q3: Where does most of your information live? One of: Paper / Spreadsheets / Software, for example QuickBooks / In people's heads / A mix. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / info_lives_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: Where does most of your information live?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / job_start
        Added value: +{
+  "description": "Operator. Q2: How does a normal job start? One of: A customer calls or texts / They walk in / They order online / A repeat or contract customer / We go out and find them. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / job_start_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: How does a normal job start?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • removedInput schema / properties / links
        Removed value: -{
-  "additionalProperties": {
-    "maxLength": 2000,
-    "type": "string"
-  },
-  "description": "Talent. Keys: linkedin, github, website, other_links.",
-  "propertyNames": {
-    "type": "string"
-  },
-  "type": "object"
-}
      • addedInput schema / properties / live_now
        Added value: +{
+  "description": "Talent. Q2: Where do you live now? One of: Lewis County / Elsewhere in the North Country / Elsewhere in New York / Outside New York. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / live_now_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: Where do you live now?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • changedInput schema / properties / name / description
        Previous value: -"Name, as the person gave it. Required."New value: +"Q7. Name, as the person gave it. Required."
      • removedInput schema / properties / origin
        Removed value: -{
-  "description": "Both. Client: When did this problem start costing you time? Talent: When did you start building on your own, and why? Max 1200 characters.",
-  "maxLength": 5000,
-  "type": "string"
-}
      • removedInput schema / properties / projects
        Removed value: -{
-  "description": "List of entries. Keys: name, link, what_it_is.",
-  "items": {
-    "additionalProperties": {
-      "maxLength": 4000,
-      "type": "string"
-    },
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  "maxItems": 20,
-  "type": "array"
-}
      • removedInput schema / properties / publications
        Removed value: -{
-  "description": "List of entries. Keys: title, venue, year, link.",
-  "items": {
-    "additionalProperties": {
-      "maxLength": 4000,
-      "type": "string"
-    },
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  "maxItems": 20,
-  "type": "array"
-}
      • removedInput schema / properties / result_90_days
        Removed value: -{
-  "description": "Client. A good result in 90 days. The owner's words.",
-  "maxLength": 4000,
-  "type": "string"
-}
      • removedInput schema / properties / resume_link
        Removed value: -{
-  "description": "Talent. Optional resume link.",
-  "maxLength": 500,
-  "type": "string"
-}
      • removedInput schema / properties / status
        Removed value: -{
-  "description": "Both. Where are you right now? Client: We do it by hand / We use a tool that falls short / We tried a fix that did not work / Not sure where to start. Talent: In school / Working full-time / Working part-time / Building my own thing / Between things.",
-  "maxLength": 100,
-  "type": "string"
-}
      • removedInput schema / properties / story
        Removed value: -{
-  "description": "Talent. Required. Most impressive thing built or done. Max 1200 characters.",
-  "maxLength": 5000,
-  "type": "string"
-}
      • removedInput schema / properties / story_link
        Removed value: -{
-  "description": "Talent. Optional link for the story.",
-  "maxLength": 500,
-  "type": "string"
-}
      • removedInput schema / properties / task
        Removed value: -{
-  "description": "Client. One of: Scheduling and bookings / Orders and inventory / Billing and payments / Customer calls, texts, and email / Reports and paperwork / Other.",
-  "maxLength": 100,
-  "type": "string"
-}
      • removedInput schema / properties / task_other
        Removed value: -{
-  "description": "Client. Required if task is Other.",
-  "maxLength": 2000,
-  "type": "string"
-}
      • changedInput schema / properties / town / description
        Previous value: -"Client. Town of the business."New value: +"Q7. Town. Optional."
      • changedInput schema / properties / track / description
        Previous value: -"client or talent. Required."New value: +"What best describes you? client = \"Operator: I make decisions inside of a business\", talent = \"Talent: I am talented and would like to talk\". Required."
      • removedInput schema / properties / when
        Removed value: -{
-  "description": "Both. Client: When do you want this fixed? As soon as possible / Within 3 months / 3 to 6 months / 6 to 12 months / Just looking. Talent: When could you start? Already full-time / Within 3 months / 3 to 6 months / 6 to 12 months / Still exploring.",
-  "maxLength": 100,
-  "type": "string"
-}
      • removedInput schema / properties / who
        Removed value: -{
-  "description": "Client. One of: The owner / One staff member / Several staff / An outside service.",
-  "maxLength": 100,
-  "type": "string"
-}
      • addedInput schema / properties / why_started
        Added value: +{
+  "description": "Operator. Q4: Why did you start or take on this business? One of: I built it / Family business / I bought it / I saw a need in town. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / why_started_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: Why did you start or take on this business?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / work_kind
        Added value: +{
+  "description": "Talent. Q1: What kind of work do you do? One of: Software / Engineering or science / Trades / Design or media / Business or operations. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / work_kind_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: What kind of work do you do?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / work_link
        Added value: +{
+  "description": "Q7, Talent only. Link to their work. Optional.",
+  "maxLength": 500,
+  "type": "string"
+}
      • addedInput schema / properties / work_want
        Added value: +{
+  "description": "Talent. Q3: What kind of work do you want? One of: Full time / Part time / One project / Not sure yet. Or the person's own typed words. Optional.",
+  "maxLength": 1200,
+  "type": "string"
+}
      • addedInput schema / properties / work_want_more
        Added value: +{
+  "description": "Optional. The person's typed answer to your follow-up after Q: What kind of work do you want?",
+  "maxLength": 1200,
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "email",
-  "name",
-  "track",
-  "review_shown",
-  "legal_and_privacy_shown",
-  "person_said_yes"
-]New value: +[
+  "track",
+  "name",
+  "email",
+  "review_shown",
+  "legal_and_privacy_shown",
+  "person_said_yes"
+]
  3. 5 tool updates
    • First observedask_with_picker
    • First observedcheck_draft
    • First observedget_offerings
    • First observedget_questions
    • First observedsubmit

Related MCP Connectors

Related MCP Servers

  • QueryQuarry

    QueryQuarryofficial

    QueryQuarry
    A
    license
    Not graded
    quality
    D
    maintenance
    Consent-based, double-blind talent marketplace. Recruiters' AI assistants search an anonymous corpus of opted-in candidates in natural language, evaluate match cards, and request contact — identity is revealed only when the candidate chooses to respond. Hosted remote server (streamable HTTP + OAuth) at queryquarry.com/api/mcp.
    MIT

  • Masumi Agent Manager

    masumi-network
    -
    license
    Not graded
    quality
    D
    maintenance
    Connects AI clients to decentralized agent discovery, hiring, monitoring, and payment systems on the Masumi Network.
    6
    -
  • Lemon-io

    Lemon-ioofficial

    lemon-io
    F
    license
    Not graded
    quality
    C
    maintenance
    Generate tailored job descriptions, hire senior developers and pull technical interview questions without leaving the conversation.
    48
    -

  • m3x-mcp-server

    Brano80
    A
    license
    Not graded
    quality
    D
    maintenance
    Connect any AI agent to M3X — the private pool matching protocol for agent-to-agent deal flow. Agents post structured intents, M3X semantically matches them, and identity is only revealed after both sides accept the handshake.
    MIT
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.

Resources